Description
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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NWeakness enumeration
Affected software
| Vendor | Product | Versions |
|---|---|---|
| curl | curl | >= 8.11.0, < 8.14.2; >= 8.15.0, < 8.16.1; >= 8.17.0, < 8.20.1 |
| curl | curl | >= 962097b8dd44ed5b9e7984bc1cdffdbdd566857f, < 7b9613fa9b1a5e04301a3920eef58e8138dad05e |
| curl | curl | 8.20.0; 8.19.0; 8.18.0; 8.17.0; 8.16.0; 8.15.0; 8.14.1; 8.14.0; 8.13.0; 8.12.1; 8.12.0; 8.11.1; 8.11.0 |
References
- https://curl.se/docs/CVE-2026-9545.htmlPatch, Vendor Advisory
- https://curl.se/docs/CVE-2026-9545.jsonVendor Advisory
- https://hackerone.com/reports/3752888Exploit, Issue Tracking, Third Party Advisory
- https://hackerone.com/reports/3752888Exploit, Issue Tracking, Third Party Advisory
Timeline
- Published
- Jul 3, 2026
- Last modified
- Sep 15, 2026
- NVD status
- Modified