Vulnerability Description
libcurl supports *pinning* of the server certificate public key for HTTPS transfers. Due to an omission, this check is not performed when connecting with QUIC for HTTP/3, when the TLS backend is wolfSSL. Documentation says the option works with wolfSSL, failing to specify that it does not for QUIC and HTTP/3. Since pinning makes the transfer succeed if the pin is fine, users could unwittingly connect to an impostor server without noticing.
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Haxx | Curl | >= 8.5.0, < 8.14.0 |
Related Weaknesses (CWE)
References
- https://curl.se/docs/CVE-2025-5025.htmlVendor Advisory
- https://curl.se/docs/CVE-2025-5025.jsonVendor Advisory
- https://hackerone.com/reports/3153497ExploitIssue TrackingThird Party Advisory
- http://www.openwall.com/lists/oss-security/2025/05/28/5Mailing ListThird Party Advisory
FAQ
What is CVE-2025-5025?
CVE-2025-5025 is a vulnerability with a CVSS score of 4.8 (MEDIUM). libcurl supports *pinning* of the server certificate public key for HTTPS transfers. Due to an omission, this check is not performed when connecting with QUIC for HTTP/3, when the TLS backend is wolfS...
How severe is CVE-2025-5025?
CVE-2025-5025 has been rated MEDIUM with a CVSS base score of 4.8/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2025-5025?
Check the references section above for vendor advisories and patch information. Affected products include: Haxx Curl.