Production debug unlock via missing device binding
Published Aug 4, 2026 · Updated Aug 4, 2026
Authentication bypass in Caliptra Core ROM and Core Firmware allows local users to unlock production debug on an unintended device. The validate_debug_unlock_token() path verifies the signature and nonce but does not compare the token's signed UDI with the target device's UDI. Exploitation requires subsystem mode and access to the integrator's signing service for a shared key hash, limiting impact to devices under that authority.
Summary
What happened
Authentication bypass in Caliptra Core ROM and Core Firmware allows local users to unlock production debug on an unintended device. The validate_debug_unlock_token() path verifies the signature and nonce but does not compare the token's signed UDI with the target device's UDI. Exploitation requires subsystem mode and access to the integrator's signing service for a shared key hash, limiting impact to devices under that authority.
The record
- CVE
- CVE-2026-11836
- Published
- Aug 4, 2026
- Updated
- Aug 4, 2026
- Vendor
- Caliptra
- Product
- Core ROM
- Classifications
- CWE-345, CAPEC-115
- 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.0.0 <=2.0.2
- Affected versionversion=2.1.0 <=2.1.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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