VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

curl: vulnerability history, versions and safety

curl is a package in the Debian ecosystem. Vulert records 15 vulnerabilities for it across 16 releases, from Apr 2015 to Sep 2019. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
15 vulnerabilities recorded U15
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 12 Sep 2019. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 15 vulnerabilities on record across 4 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 15 over 4 years · 0 in the last year i
  • Latest disclosure 12 Sep 2019 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 16 of 16 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2015 1
  • 2016 3
  • 2017 3
  • 2018 5
  • 2019 3

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

03 Vulnerabilities

Recorded vulnerabilities for curl

The 5 most severe of 15 vulnerabilities recorded for this package

Search all 15 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
cURL - Out-of-bounds Read and Data Leakage Vulnerabilities N/A unrated 7.38.0-4+deb8u9 26 Jan 2018
cURL - Multiple Vulnerabilities N/A unrated 7.38.0-4+deb8u6 06 Oct 2017
cURL - Out-of-Bounds Read Vulnerability N/A unrated 7.38.0-4+deb8u7 27 Oct 2017
cURL - Buffer Overrun and Out-of-Bounds Read Vulnerabilities N/A unrated 7.38.0-4+deb8u8 29 Nov 2017
Security Update for curl N/A unrated 7.38.0-4+deb8u11 16 May 2018

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 15 vulnerabilities for curl in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 15 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?

15 vulnerabilities are recorded for curl in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 15 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 29 Apr 2015. 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.