Vulnerability Database · Debian · Package report

curl: vulnerability history, versions and safety

curl is a package in the Debian ecosystem. Vulert records 26 vulnerabilities for it across 88 releases, from Nov -0001 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
26 vulnerabilities recorded U26
i
15 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
15 in the last 12 months

Most recent disclosure 14 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on curl i

Updated on 23 Oct 2026

Careful: 15 of the 26 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 26 vulnerabilities on record across 2026 years, 15 in the last year.

What to do: Plan around the 15 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 26 over 2026 years · 15 in the last year i
  • Latest disclosure 14 Oct 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 15 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.

i
Version Vulert vulnerabilities Fix published Details
8.23.0-1 U4 No Details →
8.23.0~rc3-1 U5 No Details →
8.23.0~rc3-1+exp1 U5 No Details →
8.23.0~rc2-1 U5 No Details →
8.23.0~rc2-1+exp1 U5 No Details →
8.23.0~rc1-2 U5 No Details →
8.23.0~rc1-1 U5 No Details →
8.22.0-1 U8 No Details →
8.22.0-1+exp1 U5 No Details →
8.22.0~rc3-1 U8 No Details →
8.22.0~rc3-1+exp1 U8 No Details →
8.22.0~rc2-2 U8 No Details →
8.22.0~rc2-1 U8 No Details →
8.21.0-2 U8 No Details →
8.21.0-2~bpo13+1 U8 No Details →
8.21.0-2+exp1 U8 No Details →
8.21.0-1 U8 No Details →
8.21.0-1+exp1 U8 No Details →
8.21.0~rc3-1 U12 No Details →
8.21.0~rc3-1+exp1 U12 No Details →
8.21.0~rc2-1 U12 No Details →
8.21.0~rc2-1+exp1 U12 No Details →
8.21.0~rc1-1+exp1 U12 No Details →
8.20.0-5 U12 No Details →
8.20.0-5~bpo13+1 U12 No Details →
8.20.0-4 U12 No Details →
8.20.0-3 U12 No Details →
8.20.0-2 U12 No Details →
8.20.0-2~bpo13+1 U12 No Details →
8.20.0-2+exp1 U12 No Details →
8.20.0-1 U12 No Details →
8.20.0-1+exp U12 No Details →
8.20.0~rc3-1 U12 No Details →
8.20.0~rc3-1+exp1 U12 No Details →
8.20.0~rc2-1 U12 No Details →
8.20.0~rc2-1+exp1 U12 No Details →
8.20.0~rc1-1+exp3 U12 No Details →
8.20.0~rc1-1+exp2 U12 No Details →
8.20.0~rc1-1+exp1 U12 No Details →
8.19.0-3 U12 No Details →
8.19.0-3+exp2 U12 No Details →
8.19.0-3+exp1 U12 No Details →
8.19.0-2 U12 No Details →
8.19.0-1 U13 No Details →
8.19.0-1~bpo13+1 U12 No Details →
8.19.0-1+exp1 U12 No Details →
8.19.0~rc3-1 U13 No Details →
8.19.0~rc2-2 U13 No Details →
8.19.0~rc2-1 U13 No Details →
8.19.0~rc1-1~exp1 U13 No Details →
8.18.0-2 U13 No Details →
8.18.0-1 U13 No Details →
8.18.0-1~bpo13+1 U13 No Details →
8.18.0~rc3-1 U14 No Details →
8.18.0~rc2-1 U14 No Details →
8.18.0~rc1-1+exp1 U14 No Details →
8.17.0-3 U14 No Details →
8.17.0-2 U14 No Details →
8.17.0-1 U14 No Details →
8.17.0~rc3-1 U15 No Details →
8.17.0~rc2-1 U15 No Details →
8.17.0~rc1-1~exp1 U15 No Details →
8.16.0-4 U15 No Details →
8.16.0-4~bpo13+1 U15 No Details →
8.16.0-3 U15 No Details →
8.16.0-2 U15 No Details →
8.16.0-1 U15 No Details →
8.16.0-1~bpo13+1 U15 No Details →
8.16.0-1+exp1 U15 No Details →
8.16.0~rc3-1 U15 No Details →
8.16.0~rc2-2 U15 No Details →
8.16.0~rc2-1 U15 No Details →
8.16.0~rc1-1~exp1 U15 No Details →
8.15.0-1 U15 No Details →
8.15.0-1~bpo13+1 U15 No Details →
8.15.0-1~exp1 U15 No Details →
8.15.0~rc3-1~exp1 U15 No Details →
8.15.0~rc2-1~exp1 U15 No Details →
8.15.0~rc1-1exp1 U15 No Details →
8.14.1-2 U16 No Details →
8.14.1-2+deb13u7 U5 No Details →
8.14.1-2+deb13u5 U9 No Details →
8.14.1-2+deb13u4 U9 No Details →
8.14.1-2+deb13u3 U13 No Details →
8.14.1-2+deb13u2 U15 No Details →
8.14.1-2+deb13u2~bpo13+1 U14 No Details →
8.14.1-2+deb13u1 U15 No Details →
8.14.1-2+exp1 U15 No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 0 1
  • 2024 5
  • 2025 6
  • 2026 14

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

03 Vulnerabilities

Recorded vulnerabilities for curl

The 5 most severe of 26 vulnerabilities recorded for this package

Search all 26 in the database →

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 26 vulnerabilities for curl in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 26 not yet rated. 15 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does curl have?

26 vulnerabilities are recorded for curl in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 26 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?

15 vulnerabilities were recorded for curl in the last 12 months, and the oldest entry in this database dates to 30 Nov -0001. 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.