Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2026-46728: U-Boot FIT Signature Verification Bypass

Published May 16, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.8High · v3.1
EPSS0.21%12th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendors
PengutronixDenx
IdentifiersCVE-2026-46728CWE-347

U-Boot versions before 2026.04 contain a FIT signature-verification flaw in which the hashed-nodes property is omitted from the protected hash. Because the verifier does not cryptographically bind the complete node-path information used to define the signed FIT content, a crafted FIT image can pass signature verification despite containing content or structure that should have caused rejection.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

An attacker able to supply a crafted FIT image may bypass FIT authenticity verification and cause U-Boot to accept an image that is not authorized under the expected signing policy. Depending on the platform boot configuration and the FIT components selected for boot, this can enable execution of attacker-controlled boot-stage, kernel, device-tree, or related boot content, undermining Secure Boot.

Mitigation

If you can’t patch tonight, do this now.

Until an updated U-Boot build can be deployed, restrict physical and logical access to boot media and firmware-update paths, permit FIT images only from tightly controlled trusted update mechanisms, and enforce hardware-rooted boot verification at earlier stages where available. Do not rely on vulnerable U-Boot FIT verification alone to establish image authenticity.

Remediation

Patch, then assume compromise.

Upgrade U-Boot to version 2026.04 or a vendor-maintained release incorporating the fix for CVE-2026-46728. Ensure deployed bootloaders verify FIT signatures using the corrected coverage of hashed-nodes and that all production signing and key-revocation policies remain enforced.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
DenxU-Bootapplication
PengutronixBareboxapplication
FAQ

Frequently asked questions

Is CVE-2026-46728 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-46728 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-46728?
Yes. As of Sep 25, 2026, Mallory has reports of a public exploit for CVE-2026-46728.
Is there a patch for CVE-2026-46728?
Upgrade U-Boot to version 2026.04 or a vendor-maintained release incorporating the fix for CVE-2026-46728. Ensure deployed bootloaders verify FIT signatures using the corrected coverage of hashed-nodes and that all production signing and key-revocation policies remain enforced.
What products are affected by CVE-2026-46728?
Denx U-Boot and Pengutronix Barebox.
How severe is CVE-2026-46728?
CVE-2026-46728 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 0.21% (12th percentile) as of Sep 25, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity7Community discussion across Reddit, Mastodon, and other social sources.