CVE Tools

CVE-2026-86409

stale SigV4 headers sent unintended

No known exploitation. EPSS puts it in the 66th percentile. No fix published yet.

Check it yourself

OpenVAS · 5 checks

e.g. OID 1.3.6.1.4.1.25623.1.1.10.2026.0515

Run the check

Published Updated Sources: CVE.org, NVD

What to do

No fixed build or workaround is published yet. Limit exposure and watch for a patch.

  • CurlAffected: ≥ 8.21.0, ≤ 8.21.0Upgrade to: after 8.21.0Affected: ≥ 8.20.0, ≤ 8.20.0Upgrade to: after 8.20.0Affected: ≥ 8.19.0, ≤ 8.19.0Upgrade to: after 8.19.0Affected: ≥ 8.18.0, ≤ 8.18.0Upgrade to: after 8.18.0 + 46 more branchesStated by: CVE record

Versions as the sources state them. Full version matrix after sign-in

Steps

Written by AI from the record
  1. Ask your developer or vendor whether any of your software uses curl's AWS SigV4 authentication feature (common in tools that talk to Amazon S3 or similar cloud storage).
  2. If so, ask them to confirm whether the application reuses the same curl connection handle for multiple requests to different URLs.
  3. Since no official fixed version is available yet, ask your developer to add code that explicitly resets or closes the curl handle after any SigV4-authenticated request, instead of relying on setting CURLOPT_AWS_SIGV4 to NULL.
  4. Watch for a curl security update addressing this issue and apply it as soon as it's released.

What it is

From the CVE record

Setting `CURLOPT_AWS_SIGV4` to NULL but does not disable SigV4 authentication, contrary to expectations and documentation. A subsequent transfer on the same handle still sends an `Authorization: AWS4-HMAC-SHA256` header to whatever URL isset next, leaking state information.

In plain language

Written by AI from the record

A bug in the curl software can cause your cloud account credentials to be accidentally sent to the wrong website, and there is currently no fix available, so if your business's applications use curl with Amazon-style cloud logins you should check this now.

In curl, setting CURLOPT_AWS_SIGV4 to NULL does not disable AWS SigV4 authentication as documented, so a reused transfer handle can leak a stale Authorization: AWS4-HMAC-SHA256 header—containing signed credential material—to a subsequent, unintended URL (CWE-201, information exposure through sent data).

If you're affected

  • Cloud credential leakage
  • Unauthorized access to cloud resources
  • Data exposure to third-party endpoints
  • Regulatory/compliance exposure
  • Reputational damage from leaked secrets

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS66th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

1.1% chance of exploitation activity in the next 30 days, which ranks it in the 66th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

6 events over 9 days, from the signal feeds we watch.

  1. Record updated
  2. OpenVAS check addedrecord updated
  3. Publishedweakness classified, record updated

Affected products

Technical detail

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Scored 8.1 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity HighRequires specific conditions like a race condition or non-default configuration
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Curl, not every advisory.