CVE-2025-5025

No QUIC certificate pinning with wolfSSL

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.

4.8
CVSS
Severity: Medium
CVSS 3.1 •
EPSS 0.01%
Affected: curl curl
Published at:
Updated at:

References

Frequently Asked Questions

What is the severity of CVE-2025-5025?
CVE-2025-5025 has been scored as a medium severity vulnerability.
How to fix CVE-2025-5025?
To fix CVE-2025-5025, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2025-5025 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2025-5025 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2025-5025?
CVE-2025-5025 affects curl curl.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.