CVE-2025-5025
libcurl wolfSSL QUIC Certificate Pinning Bypass
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.
INFO
Published Date :
May 28, 2025, 7:15 a.m.
Last Modified :
July 30, 2025, 7:41 p.m.
Remotely Exploit :
Yes !
Source :
2499f714-1537-4658-8207-48ae4bb9eae9
CVSS Scores
Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
---|---|---|---|---|---|---|
CVSS 3.1 | MEDIUM | 134c704f-9b21-4f2e-91b3-4a467353bcc0 |
Solution
CVE-2025-5025
vulnerability.
Public PoC/Exploit Available at Github
CVE-2025-5025 has a 3 public
PoC/Exploit
available at Github.
Go to the Public Exploits
tab to see the list.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2025-5025
.
URL | Resource |
---|---|
https://curl.se/docs/CVE-2025-5025.html | Vendor Advisory |
https://curl.se/docs/CVE-2025-5025.json | Vendor Advisory |
https://hackerone.com/reports/3153497 | Exploit Issue Tracking Third Party Advisory |
http://www.openwall.com/lists/oss-security/2025/05/28/5 | Mailing List Third Party Advisory |
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2025-5025
is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2025-5025
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
None
Dockerfile
None
Makefile Smarty Dockerfile Shell HCL JavaScript Go HTML TypeScript CSS
📡 PoC auto collect from GitHub. ⚠️ Be careful Malware.
security cve exploit poc vulnerability
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2025-5025
vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2025-5025
vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
Initial Analysis by [email protected]
Jul. 30, 2025
Action Type Old Value New Value Added CWE CWE-295 Added CPE Configuration OR *cpe:2.3:a:haxx:curl:*:*:*:*:*:*:*:* versions from (including) 8.5.0 up to (excluding) 8.14.0 Added Reference Type CVE: http://www.openwall.com/lists/oss-security/2025/05/28/5 Types: Mailing List, Third Party Advisory Added Reference Type curl: https://curl.se/docs/CVE-2025-5025.html Types: Vendor Advisory Added Reference Type curl: https://curl.se/docs/CVE-2025-5025.json Types: Vendor Advisory Added Reference Type curl: https://hackerone.com/reports/3153497 Types: Exploit, Issue Tracking, Third Party Advisory -
CVE Modified by 134c704f-9b21-4f2e-91b3-4a467353bcc0
May. 30, 2025
Action Type Old Value New Value Added CVSS V3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N -
CVE Modified by af854a3a-2127-422b-91ae-364da2661108
May. 28, 2025
Action Type Old Value New Value Added Reference http://www.openwall.com/lists/oss-security/2025/05/28/5 -
New CVE Received by 2499f714-1537-4658-8207-48ae4bb9eae9
May. 28, 2025
Action Type Old Value New Value Added 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. Added Reference https://curl.se/docs/CVE-2025-5025.html Added Reference https://curl.se/docs/CVE-2025-5025.json Added Reference https://hackerone.com/reports/3153497