Vulnerability Database · Debian · Package report

dracut: vulnerability history, versions and safety

dracut is a package in the Debian ecosystem. Vulert records 7 vulnerabilities for it across 97 releases, from Oct 2012 to Aug 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
7 vulnerabilities recorded U7
i
3 with no fix published

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

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

Most recent disclosure 07 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on dracut i

Updated on 23 Oct 2026

Careful: 3 of the 7 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 7 vulnerabilities on record across 13 years, 3 in the last year.

What to do: Plan around the 3 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 7 over 13 years · 3 in the last year i
  • Latest disclosure 07 Aug 2026 i
  • Highest CVSS 7.8 i
  • With no published fix 3 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 dracut, 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
112-1 U1 No Details →
111-6 U2 No Details →
111-5 U2 No Details →
111-4 U2 No Details →
111-3 U2 No Details →
111-2 U3 No Details →
111-1 U3 No Details →
110-12 U3 No Details →
110-11 U3 No Details →
110-10 U3 No Details →
110-9 U3 No Details →
110-8 U3 No Details →
110-7 U3 No Details →
110-6 U3 No Details →
110-5 U3 No Details →
110-4 U3 No Details →
110-3 U3 No Details →
110-2 U3 No Details →
110-1 U3 No Details →
109-11 U3 No Details →
109-10 U3 No Details →
109-9 U3 No Details →
109-8 U3 No Details →
109-7 U3 No Details →
109-6 U3 No Details →
109-6exp3 U3 No Details →
109-6exp2 U3 No Details →
109-6exp1 U3 No Details →
109-5 U3 No Details →
109-4 U3 No Details →
109-3 U3 No Details →
109-2 U3 No Details →
109-1 U3 No Details →
109-1exp1 U3 No Details →
108-8 U3 No Details →
108-7 U3 No Details →
108-6 U3 No Details →
108-5 U3 No Details →
108-4 U3 No Details →
108-3 U3 No Details →
108-2 U3 No Details →
108-1 U3 No Details →
107-2 U3 No Details →
107-1 U3 No Details →
106-6 U3 No Details →
106-5 U3 No Details →
106-5~bpo12+1 U3 No Details →
106-4 U3 No Details →
106-3 U3 No Details →
106-2 U3 No Details →
106-1 U3 No Details →
105-3 U3 No Details →
105-2 U3 No Details →
105-2~exp8 U3 No Details →
105-2~exp7 U3 No Details →
105-2~exp6 U3 No Details →
105-2~exp5 U3 No Details →
105-2~exp4 U3 No Details →
105-2~exp3 U3 No Details →
105-2~exp2 U3 No Details →
105-2~exp1 U3 No Details →
105-1 U3 No Details →
103-2 U3 No Details →
103-1.1 U3 No Details →
103-1 U3 No Details →
102-3 U3 No Details →
102-2 U3 No Details →
102-1 U3 No Details →
060+5-8 U3 No Details →
060+5-7 U3 No Details →
060+5-2~exp1 U3 No Details →
060+5-1 U3 No Details →
059+212-4 U3 No Details →
059+212-3 U3 No Details →
059+212-2 U3 No Details →
059+212-1 U3 No Details →
059-4 U3 No Details →
059-3 U3 No Details →
059-3~bpo11+1 U3 No Details →
059-2 U3 No Details →
059-2~bpo11+1 U3 No Details →
059-1 U3 No Details →
059-1~bpo11+1 U3 No Details →
057+157-4 U3 No Details →
057+157-4~bpo11+1 U3 No Details →
057+157-3 U3 No Details →
057+157-3~bpo11+1 U3 No Details →
057+157-2 U3 No Details →
057+157-2~bpo11+1 U3 No Details →
057+157-1 U3 No Details →
057+157-1~bpo11+1 U3 No Details →
056-3 U3 No Details →
056-3~bpo11+1 U3 No Details →
056-2 U3 No Details →
056-1 U3 No Details →
055-1 U3 No Details →
051-1 U3 No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2012 2
  • 2018 2
  • 2026 3

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

03 Vulnerabilities

Recorded vulnerabilities for dracut

The 5 most severe of 7 vulnerabilities recorded for this package

Search all 7 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 dracut

Is dracut safe to use?

Vulert records 7 vulnerabilities for dracut in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 7 not yet rated. 3 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does dracut have?

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

3 vulnerabilities were recorded for dracut in the last 12 months, and the oldest entry in this database dates to 09 Oct 2012. 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 dracut 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 dracut for upcoming vulnerabilities?

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