Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-86409

stale SigV4 headers sent unintended

Description

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.

Public exploit

An exploit or proof of concept is public: anyone can try it against an unpatched system. A reference of the record is tagged as an exploit. CISA's SSVC rates its exploitation: a proof of concept is public.

Show the exploits1

References tagged exploit1 reference

Timeline

  1. ID reserved

    By curl

  2. · 43 days later

    Published

  3. · 9 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-86409, by who scored it
Scored byCVSSScoreVector
CISA-ADPADP (enrichment)3.1High8.1CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Awaiting Analysis3.1High8.1CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
1.1% · top 34% of all CVEs (11 Nov 2026)
CISA SSVC
Exploitation: poc · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.1.

Affected products

  • curl · curl

    • affected 8.21.0 – ≤ 8.21.0
    • affected 8.20.0 – ≤ 8.20.0
    • affected 8.19.0 – ≤ 8.19.0
    • affected 8.18.0 – ≤ 8.18.0
    • affected 8.17.0 – ≤ 8.17.0
    • affected 8.16.0 – ≤ 8.16.0
    • affected 8.15.0 – ≤ 8.15.0
    • affected 8.14.1 – ≤ 8.14.1
    • affected 8.14.0 – ≤ 8.14.0
    • affected 8.13.0 – ≤ 8.13.0
    • affected 8.12.1 – ≤ 8.12.1
    • affected 8.12.0 – ≤ 8.12.0
    • affected 8.11.1 – ≤ 8.11.1
    • affected 8.11.0 – ≤ 8.11.0
    • affected 8.10.1 – ≤ 8.10.1
    • affected 8.10.0 – ≤ 8.10.0
    • affected 8.9.1 – ≤ 8.9.1
    • affected 8.9.0 – ≤ 8.9.0
    • affected 8.8.0 – ≤ 8.8.0
    • affected 8.7.1 – ≤ 8.7.1
    • affected 8.7.0 – ≤ 8.7.0
    • affected 8.6.0 – ≤ 8.6.0
    • affected 8.5.0 – ≤ 8.5.0
    • affected 8.4.0 – ≤ 8.4.0
    • affected 8.3.0 – ≤ 8.3.0
    • affected 8.2.1 – ≤ 8.2.1
    • affected 8.2.0 – ≤ 8.2.0
    • affected 8.1.2 – ≤ 8.1.2
    • affected 8.1.1 – ≤ 8.1.1
    • affected 8.1.0 – ≤ 8.1.0
    • affected 8.0.1 – ≤ 8.0.1
    • affected 8.0.0 – ≤ 8.0.0
    • affected 7.88.1 – ≤ 7.88.1
    • affected 7.88.0 – ≤ 7.88.0
    • affected 7.87.0 – ≤ 7.87.0
    • affected 7.86.0 – ≤ 7.86.0
    • affected 7.85.0 – ≤ 7.85.0
    • affected 7.84.0 – ≤ 7.84.0
    • affected 7.83.1 – ≤ 7.83.1
    • affected 7.83.0 – ≤ 7.83.0
    • and 10 more

References

References3

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-86409 badge
[![CVE-2026-86409](https://cveledger.app/badge/CVE-2026-86409.svg)](https://cveledger.app/cve/CVE-2026-86409)

Record last updated .