Secure-boot bypass via unchecked AXI staging address
Published Aug 4, 2026 · Updated Aug 4, 2026
Secure-boot bypass in Caliptra Core ROM 2.1.0 through 2.1.1 allows local users to execute modified firmware during subsystem update reset. UpdateResetFlow::run() accepts the firmware address from per-command mailbox fields without checking it against SS_EXTERNAL_STAGING_AREA_BASE_ADDR and does not reverify the ICCM image after loading. Exploitation requires compromised MCU firmware with AXI-manager access to unprotected SRAM, and attestation continues to report the originally verified digest.
Summary
What happened
Secure-boot bypass in Caliptra Core ROM 2.1.0 through 2.1.1 allows local users to execute modified firmware during subsystem update reset. UpdateResetFlow::run() accepts the firmware address from per-command mailbox fields without checking it against SS_EXTERNAL_STAGING_AREA_BASE_ADDR and does not reverify the ICCM image after loading. Exploitation requires compromised MCU firmware with AXI-manager access to unprotected SRAM, and attestation continues to report the originally verified digest.
The record
- CVE
- CVE-2026-11835
- Published
- Aug 4, 2026
- Updated
- Aug 4, 2026
- Vendor
- Caliptra
- Product
- Core ROM
- Classifications
- CWE-20, CWE-367, CAPEC-29, T1553
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Aug 4, 2026CVE publishedPublication date reported by the CVE source.
- Aug 4, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.1.0 <=2.1.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo