CVE-2025-5025
libcurl supports *pinning* of the server certificate public key for HTTPS transfers.
Does this matter?
Lower severity and a low EPSS score (0.29%). Track it; it rarely justifies an emergency change on its own.
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 3.1
- 4.8 MEDIUMCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
- EPSS
- 0.29% probability · 22th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-295
- Affected
- haxx/curl
- Source
- 2499f714-1537-4658-8207-48ae4bb9eae9
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
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.