Curl

Vendor:

First CVE: May 2, 2005 · Active for 21 years

199
Total CVEs
More Total CVEs than 99% of tracked products
12.4
Avg CVEs / Year
Higher CVE frequency than 96% of tracked products
6.9
Avg CVSS
Higher Avg CVSS than 43% of tracked products
0.0%
KEV Rate
Bottom 1%

Trends Over Time

The number and severity of CVEs published that impact Curl over time

Volume of CVEsAvg CVSS Base Score
First CVE
May 2, 2005
21 years ago
Most Recent CVE
Jul 3, 2026
25 days ago

CVE Severity & Scoring

Curl199 CVEs
All CVEs352,785 CVEs
LowMediumHighCritical
Attack Vector
Local8 (4.0%)
Network167 (83.9%)
Unknown23 (11.6%)
Physical1 (0.5%)
Adjacent Network0 (0.0%)
Attack Complexity
Low134 (67.3%)
High42 (21.1%)
Unknown23 (11.6%)
User Interaction
None150 (75.4%)
Unknown23 (11.6%)
Required26 (13.1%)
Privileges Required
Low19 (9.5%)
High0 (0.0%)
None157 (78.9%)
Unknown23 (11.6%)

Top CVEs

Signals from CVEs in this product scope (199 CVEs).

199 CVEs · Highest risk first

CVEPublishedCVSSRiskKEVExploit
This flaw makes curl overflow a heap based buffer in the SOCKS5 proxy handshake. When curl is asked to pass along the host name to the SOCKS5 proxy to allow that to resolve the ad
Oct 18, 20239.876NONO
The SSL protocol, as used in certain configurations in Microsoft Windows and Microsoft Internet Explorer, Mozilla Firefox, Google Chrome, Opera, and other products, encrypts data b
Sep 6, 20114.371NOYES
curl 7.75.0 through 7.76.1 suffers from a use-after-free vulnerability resulting in already freed memory being used when a TLS 1.3 session ticket arrives over a connection. A malic
Jun 11, 20218.160NONO
When curl retrieves an HTTP response, it stores the incoming headers so that they can be accessed later via the libcurl headers API. However, curl did not have a limit in how many
Sep 15, 20237.559NONO
When an application tells libcurl it wants to allow HTTP/2 server push, and the amount of received headers for the push surpasses the maximum allowed limit (1000), libcurl aborts t
Mar 27, 20248.646NONO
A heap buffer overflow in the TFTP receiving code allows for DoS or arbitrary code execution in libcurl versions 7.19.4 through 7.64.1.
May 28, 20197.846NONO
Stack-based buffer overflow in the Curl_sasl_create_digest_md5_message function in lib/curl_sasl.c in curl and libcurl 7.26.0 through 7.28.1, when negotiating SASL DIGEST-MD5 authe
Mar 8, 20137.544NOYES
libcurl had a flaw that when instructed to clear proxy authentication credentials which made it not do so, leaving the old credentials around to get used for subsequent transfers t
Jul 3, 20269.843NONO
The curl logic that works with SASL authentication could end up cleaning up the GSASL context *twice* without clearing the pointer in between, making it `free()` the same pointer t
Jul 3, 20269.842NONO
A use-after-free vulnerability exists in libcurl when an application configures an HTTP/2 stream-dependency tree via `CURLOPT_STREAM_DEPENDS` or `CURLOPT_STREAM_DEPENDS_E`, subsequ
Jul 3, 20269.842NONO

Exploit Exposure

Signals from CVEs in this product scope (199 CVEs).

CISA KEV
0 CVEs
0.0% of CVEs· Bottom 1%
Metasploit
1 CVE
0.5% of CVEs· 96th percentile
Nuclei
0 CVEs
0.0% of CVEs· Bottom 1%
ExploitDB
1 CVE
0.5% of CVEs· 85th percentile

Social Chatter

Signals from CVEs in this product scope (199 CVEs).

Media Mentions

Signals from CVEs in this product scope (199 CVEs).

Top CNAs Publishing CVEs For Curl

Top CWEs

Versions

VersionCVE CountAvg CVSSAvg EPSSKEVExploits
8.8.014.30.8%00
8.6.016.31.7%00
8.5.015.31.1%00
8.11.117.01.3%00
7.9.856.18.5%00
7.9.756.18.5%00
7.9.656.18.5%00
7.9.556.18.5%00
7.9.456.18.5%00
7.9.356.18.5%00
7.9.256.18.5%00
7.9.156.18.5%00
7.956.18.5%00
7.88.115.91.9%00
7.88.015.91.9%00
7.83.018.13.7%00
7.8.156.18.5%00
7.856.18.5%00
7.7.356.18.5%00
7.7.256.18.5%00