Libcurl is a widely embedded HTTP transfer library used across servers, applications, and embedded systems despite its single-product scope, making it a critical supply-chain dependency where a single vulnerability can propagate broadly downstream. The durable signal centers on memory-safety issues, particularly buffer boundary violations, reflecting the parsing and protocol complexity inherent to a C-based network library. Current severity, exploitation activity, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Libcurl over time
Signals from CVEs in this vendor scope (3 CVEs).
3 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2009-2417HIGH lib/ssluse.c in cURL and libcurl 7.4 through 7.19.5, when OpenSSL is used, does not properly handle a '\0' character in a domain name in the subject's Common Name (CN) field of an | Aug 14, 2009 | 7.5 | 24 | NO | NO |
CVE-2005-3185HIGH Stack-based buffer overflow in the ntlm_output function in http-ntlm.c for (1) wget 1.10, (2) curl 7.13.2, and (3) libcurl 7.13.2, and other products that use libcurl, when NTLM au | Oct 13, 2005 | 7.5 | 21 | NO | NO |
CVE-2007-3564HIGH libcurl 7.14.0 through 7.16.3, when built with GnuTLS support, does not check SSL/TLS certificate expiration or activation dates, which allows remote attackers to bypass certain ac | Jul 18, 2007 | 7.5 | 20 | NO | NO |
Signals from CVEs in this vendor scope (3 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Libcurl.
Media articles that mention a CVE ID that affects a product developed by Libcurl — matched by CVE ID, not by vendor name.