Skip to content
Connect AISign inSign up free
CVE-2026-95457.5HighCWE-200

CVE-2026-9545: exposing HTTP/3 early data

curl

Fixed in Ubuntu 26.04, SLES 15 SP7/16.0/16.1, openSUSE Leap 16.0, Alpine 3.23/3.24 · Affected: curl · Exploitation: not established

At a glance

0.3%probability of exploitation in the next 30 days
22nd percentile
050100

Higher than 22% of scored CVEs

7.5HighCVSS
LowHigh

What it isNVD

In this scenario, libcurl first uses a proper HTTP/3 server for the initial transfers, and when it makes a second transfer to the same site it has been replaced by the attacker's impostor machine - without a valid certificate.

When libcurl returns to the hostname the second time with a cached SSL session (`CURLOPT_SSL_SESSIONID_CACHE` is not disabled) and early data enabled (the `CURLSSLOPT_EARLYDATA` bit is set in `CURLOPT_SSL_OPTIONS`), libcurl might send off the second request's bytes on that new connection *before* enforcing the certificate verification failure.

Potentially leaking sensitive information.

Fix status by distribution

From each distribution’s security tracker. Distributions we did not check are not listed.

ExploitationNot established

Not in CISA KEV as of catalogue 2026.11.20 (20 Nov)

  1. Not establishedNothing in the sources we check

Not seen so far: in CISA KEV · exploited (reported) · scanning observed · proof of concept public.

Weakness and public checks

Public check
No public nuclei template
Weakness
Information Exposure · Information Disclosure

Disclosed bug bounty reports about CVE-2026-9545

The reports on HackerOne that name this CVE, with HackerOne's own outcome. Titles and metadata only.

Other CVEs in curl

Every published CVE for curl , by how far exploitation has gone. This one is among them.

As a list
Other CVEs in curl: each mark is one CVE.Drag to move · Ctrl + scroll to zoom · a mark opens that CVE

What changed

Alpine status tracked since 5 Nov 2026. Debian status tracked since 5 Nov 2026. Red Hat status tracked since 5 Nov 2026. SUSE status tracked since 5 Nov 2026. Ubuntu status tracked since 14 Nov 2026.

  1. Ubuntu’s tracker lists Ubuntu 14.04 as not affected Ubuntu
  2. Ubuntu’s tracker lists Ubuntu 16.04 as not affected Ubuntu
  3. Ubuntu’s tracker lists Ubuntu 18.04 as not affected Ubuntu
  4. Ubuntu’s tracker lists Ubuntu 20.04 as not affected Ubuntu
  5. Ubuntu’s tracker lists Ubuntu 22.04 as not affected Ubuntu
  6. Ubuntu’s tracker lists Ubuntu 24.04 as not affected Ubuntu
  7. Ubuntu’s tracker lists Ubuntu stonking as not affected Ubuntu
  8. Seen in Alpine’s tracker on 5 Nov: Alpine 3.23 fixed in curl-8.22.0-r0 Alpine
  9. Seen in Alpine’s tracker on 5 Nov: Alpine 3.24 fixed in curl-8.21.0-r0 Alpine
  10. Debian’s tracker lists Debian 12 as not affected Debian
  11. Debian’s tracker lists Debian 13 as affected, with no fix released Debian
  12. Red Hat’s tracker lists RHEL 10 as affected, with no fix released Red Hat
  13. Red Hat’s tracker lists RHEL 6 as affected, with no fix released Red Hat
  14. Red Hat’s tracker lists RHEL 7 as affected, with no fix released Red Hat
  15. Red Hat’s tracker lists RHEL 8 as affected, with no fix released Red Hat
  16. Red Hat’s tracker lists RHEL 9 as affected, with no fix released Red Hat
  17. Seen in SUSE’s tracker on 5 Nov: openSUSE Leap 16.0 fixed in curl-8.14.1-160000.8.1 SUSE
  18. SUSE’s tracker lists SLES 12 SP4 as not affected SUSE
  19. SUSE’s tracker lists SLES 12 SP5 as not affected SUSE
  20. SUSE’s tracker lists SLES 15 SP1 as not affected SUSE

Showing the latest 20 changes.

Coverage1 article · 1 outlet

First in our coverage: Microsoft, 7 Oct.

New articles also arrive in the RSS feed.

References