Vulnerability Database · Debian · Package report

u-boot: vulnerability history, versions and safety

u-boot is a package in the Debian ecosystem. Vulert records 96 vulnerabilities for it across 53 releases, from Jun 2018 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
96 vulnerabilities recorded U96
i
23 with no fix published

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

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

Most recent disclosure 29 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on u-boot i

Updated on 23 Oct 2026

Careful: 23 of the 96 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 96 vulnerabilities on record across 8 years, 10 in the last year.

What to do: Plan around the 23 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 96 over 8 years · 10 in the last year i
  • Latest disclosure 29 Aug 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 23 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 u-boot, 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
2025.01-3.2 U7 No Details →
2025.01-3.1 U9 No Details →
2025.01-3 U23 No Details →
2025.01-2 U23 No Details →
2025.01-1 U23 No Details →
2024.01+dfsg-7 U23 No Details →
2024.01+dfsg-6 U23 No Details →
2024.01~rc6+dfsg-2 U23 No Details →
2024.01~rc6+dfsg-1 U23 No Details →
2024.01+dfsg-5 U23 No Details →
2024.01+dfsg-4 U23 No Details →
2024.01+dfsg-3 U23 No Details →
2024.01+dfsg-2 U23 No Details →
2024.01+dfsg-1 U23 No Details →
2023.07~rc5+dfsg-1 U23 No Details →
2023.07~rc4+dfsg-1 U23 No Details →
2023.07+dfsg-1 U23 No Details →
2023.04~rc5+dfsg-1 U23 No Details →
2023.04~rc2+dfsg-1 U23 No Details →
2023.04+dfsg-1 U23 No Details →
2023.01~rc4+dfsg-2 U23 No Details →
2023.01~rc4+dfsg-1 U23 No Details →
2023.01~rc3+dfsg-1 U23 No Details →
2023.01+dfsg-2 U23 No Details →
2023.01~rc2+dfsg-1 U23 No Details →
2023.01+dfsg-1 U23 No Details →
2022.10+dfsg-2 U23 No Details →
2022.10~rc2+dfsg-2 U23 No Details →
2022.10~rc2+dfsg-1 U23 No Details →
2022.10+dfsg-1 U23 No Details →
2022.07~rc4+dfsg-1 U23 No Details →
2022.07~rc3+dfsg-2 U23 No Details →
2022.07~rc3+dfsg-1 U23 No Details →
2022.07+dfsg-1 U23 No Details →
2022.04~rc4+dfsg-1 U23 No Details →
2022.04+dfsg-2 U23 No Details →
2022.04~rc2+dfsg-1 U23 No Details →
2022.04+dfsg-1 U23 No Details →
2022.01~rc4+dfsg-1 U23 No Details →
2022.01+dfsg-2 U23 No Details →
2022.01~rc2+dfsg-1 U23 No Details →
2022.01+dfsg-1 U23 No Details →
2021.10~rc5+dfsg-1 U23 No Details →
2021.10+dfsg-1 U23 No Details →
2021.07~rc4+dfsg-1 U23 No Details →
2021.07+dfsg-2 U23 No Details →
2021.07+dfsg-1 U23 No Details →
2021.04~rc4+dfsg-1 U23 No Details →
2021.04~rc3+dfsg-1 U23 No Details →
2021.01+dfsg-5 U53 No Details →
2021.01+dfsg-5+deb11u3 U7 No Details →
2021.01+dfsg-5+deb11u2 U9 No Details →
2021.01+dfsg-5+deb11u1 U24 No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 10
  • 2019 40
  • 2020 4
  • 2022 14
  • 2024 2
  • 2025 17
  • 2026 9

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

03 Vulnerabilities

Recorded vulnerabilities for u-boot

The 5 most severe of 96 vulnerabilities recorded for this package

Search all 96 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 u-boot

Is u-boot safe to use?

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

How many vulnerabilities does u-boot have?

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

10 vulnerabilities were recorded for u-boot in the last 12 months, and the oldest entry in this database dates to 26 Jun 2018. 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 u-boot 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 u-boot for upcoming vulnerabilities?

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