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.
Metrics
CVSS 3.1 4.8/10
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:NWeakness enumeration
Affected software
| Vendor | Product | Versions |
|---|---|---|
| curl | curl | >= 8.13.0, <= 8.13.0; >= 8.12.1, <= 8.12.1; >= 8.12.0, <= 8.12.0; >= 8.11.1, <= 8.11.1; >= 8.11.0, <= 8.11.0; >= 8.10.1, <= 8.10.1; >= 8.10.0, <= 8.10.0; >= 8.9.1, <= 8.9.1; >= 8.9.0, <= 8.9.0; >= 8.8.0, <= 8.8.0; >= 8.7.1, <= 8.7.1; >= 8.7.0, <= 8.7.0; >= 8.6.0, <= 8.6.0; >= 8.5.0, <= 8.5.0 |
References
- https://curl.se/docs/CVE-2025-5025.htmlVendor Advisory
- https://curl.se/docs/CVE-2025-5025.jsonVendor Advisory
- https://hackerone.com/reports/3153497Exploit, Issue Tracking, Third Party Advisory
- http://www.openwall.com/lists/oss-security/2025/05/28/5Mailing List, Third Party Advisory
Timeline
- Published
- May 28, 2025
- Last modified
- Jun 17, 2026
- NVD status
- Analyzed