Curl vulnerabilitiesRanked by how likely they are to be used.
Curl is made by Haxx. We track 111 published vulnerabilities in it, across 214 versions. None of them is on the list of flaws known to be exploited today. If you run Curl, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Curl vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Curl's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Curl flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 73%CVE-2011-3389Medium
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 by using CBC mode with chained...
- 64%CVE-2021-22901High
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.
- 58%CVE-2023-38039High
When curl retrieves an HTTP response, it stores the incoming headers so that they can be accessed later via the libcurl headers API.
- 36%CVE-2022-32206Medium
curl < 7.84.0 supports "chained" HTTP compression algorithms, meaning that a serverresponse can be compressed multiple times and potentially with different algorithms.
- 31%CVE-2022-32205Medium
A malicious server can serve excessive amounts of `Set-Cookie:` headers in a HTTP response to curl and curl < 7.84.0 stores all of them.
- 30%CVE-2015-3145High
The sanitize_cookie_path function in cURL and libcurl 7.31.0 through 7.41.0 does not properly calculate an index, which allows remote attackers to cause a denial of service (out-of-bounds write and crash) or possibly...
- 18%CVE-2019-5482Critical
Heap buffer overflow in the TFTP protocol handler in cURL 7.19.4 to 7.65.3.
- 17%CVE-2022-43551High
A vulnerability exists in curl <7.87.0 HSTS check that could be bypassed to trick it to keep using HTTP.
- 15%CVE-2021-22926High
libcurl-using applications can ask for a specific client certificate to be used in a transfer.
Running Curl? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
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 by using CBC mode with chained initialization vectors, which allows man-in-the-middle attackers to obtain plaintext HTTP headers via a blockwise chosen-boundary attack (BCBA) on an HTTPS session, in conjunction with JavaScript code that uses (1) the HTML5 WebSocket API, (2) the Java URLConnection API, or (3) the Silverlight WebClient API, aka a "BEAST" attack.
- Matched to
- Curl on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 111 published vulnerabilities listed under the name Curl, across 214 versions.
None of Curl's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Curl. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.