CVE-2026-9545

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.
References
Link Resource
https://curl.se/docs/CVE-2026-9545.html Patch Vendor Advisory
https://curl.se/docs/CVE-2026-9545.json Vendor Advisory
https://hackerone.com/reports/3752888 Exploit Issue Tracking Third Party Advisory
https://hackerone.com/reports/3752888 Exploit Issue Tracking Third Party Advisory
Configurations

Configuration 1 (hide)

cpe:2.3:a:haxx:curl:*:*:*:*:*:*:*:*

History

No history.

Information

Published : 2026-07-03 07:16

Updated : 2026-09-15 07:16


NVD link : CVE-2026-9545

Mitre link : CVE-2026-9545

CVE.ORG link : CVE-2026-9545


JSON object : View

Products Affected

haxx

  • curl
CWE
CWE-200

Exposure of Sensitive Information to an Unauthorized Actor

NVD-CWE-noinfo