VulertSecurity VulertSecurity

Vulnerability Database · OSS-Fuzz · Package report

curl: vulnerability history, versions and safety

curl is a package in the OSS-Fuzz ecosystem. Vulert records 27 vulnerabilities for it across 30 releases, from Jul 2020 to Aug 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
27 vulnerabilities recorded H7 M18 U2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all curl vulnerabilities

Vulert verdict on curl i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 20 Aug 2025. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 27 vulnerabilities on record across 5 years, none in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 27 over 5 years · 0 in the last year i
  • Latest disclosure 20 Aug 2025 i
  • Highest CVSS n/a i
  • With no published fix 0 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for curl, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

Newest 30 of 30 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 5
  • 2021 14
  • 2022 7
  • 2025 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 27 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for curl

The 5 most severe of 27 vulnerabilities recorded for this package

Search all 27 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Negative-size-param in fuzz_tlv_to_string in curl N/A unrated 25f962193574e35fe638764c3afb9d25d8a9768b 22 Jul 2020
Heap-buffer-overflow in fuzz_read_callback in curl N/A high ab6eb2ec0744074004980d0f98677e52b215941f 13 Jan 2021
Heap-buffer-overflow in setcharset in curl N/A medium 0b664ba968437715819bfe4c7ada5679d16ebbc3 13 Jan 2021
Heap-buffer-overflow in seturl in curl N/A medium ef4dc1b5be8c092550617ea0f1b9844a9cdc6ae8 21 Dec 2021
Heap-buffer-overflow in Curl_sasl_decode_mech in curl N/A medium ef4dc1b5be8c092550617ea0f1b9844a9cdc6ae8 22 Dec 2021

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About curl

Is curl safe to use?

Vulert records 27 vulnerabilities for curl in OSS-Fuzz: 0 critical, 7 high, 18 medium and 0 low, plus 2 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does curl have?

27 vulnerabilities are recorded for curl in the OSS-Fuzz ecosystem: 0 critical, 7 high, 18 medium and 0 low, plus 2 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new curl vulnerabilities disclosed?

0 vulnerabilities were recorded for curl in the last 12 months, and the oldest entry in this database dates to 01 Jul 2020. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of curl are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor curl for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the curl version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.