# CVE-2026-46728: Security feature bypass in U-Boot

> Attackers can bypass FIT signature verification in U-Boot by omitting hashed-nodes from the hash, compromising boot integrity.

- **Severity:** High 8.2 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 May 2026
- **Updated:** 18 May 2026
- **Also known as:** DEBIAN-CVE-2026-46728, GHSA-5cv5-vm4q-7wmx, UBUNTU-CVE-2026-46728

## What is CVE-2026-46728?

CVE-2026-46728 is a high-severity vulnerability in denx U-Boot, published on 16 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Das U-Boot before 2026.04 allows FIT (Flat Image Tree) signature verification bypass because hashed-nodes is omitted from a hash.

Weakness: CWE-346 (Origin Validation Error)

## Which versions are affected by CVE-2026-46728?

It affects 1 product.


Products: Denx U-Boot.

## How do I fix CVE-2026-46728?

Upgrade to a fixed version.

## Is CVE-2026-46728 being exploited?

There is no known exploitation of CVE-2026-46728 in the wild and no public exploit code.

## Other vulnerabilities in denx U-Boot

- [CVE-2022-34835](https://insights.sbomify.com/CVE-2022-34835/): Integer overflow in n/a (critical 9.8)
- [CVE-2022-30767](https://insights.sbomify.com/CVE-2022-30767/): Memory corruption in n/a (critical 9.8)
- [CVE-2020-8432](https://insights.sbomify.com/CVE-2020-8432/): Use after free in n/a (critical 9.8)
- [CVE-2019-14192](https://insights.sbomify.com/CVE-2019-14192/): Integer overflow in n/a (critical 9.8)
- [CVE-2019-14193](https://insights.sbomify.com/CVE-2019-14193/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-46728 and fix it if it is affected.

What it is: CVE-2026-46728 is a high-severity vulnerability in denx U-Boot, published on 16 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-46728 in the wild and no public exploit code.

Affected product: denx U-Boot. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-46728/ (Markdown: https://insights.sbomify.com/CVE-2026-46728/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-46728
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-46728
- OSV: https://osv.dev/vulnerability/CVE-2026-46728

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-46728/
Summaries are generated and may contain mistakes; the official description above is the record.