CVE-2026-11836: Production Debug-Unlock Token Verification Missing Device Binding
Caliptra · Core ROM
Vendor fix available · Affected: Caliptra Core ROM · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 1% of scored CVEs
DescriptionCVE.org
Insufficient verification of data authenticity in Caliptra Core ROM and Core Firmware (validate_debug_unlock_token()) in subsystem mode allows an attacker with access to the integrator's debug unlock signing service to unlock production debug on an unintended device by presenting a valid token issued for a different device sharing the same debug unlock key hash. The 384-bit challenge nonce continues to prevent replay of previously issued tokens. Practical impact is limited to loss of per-device scope enforcement within a set of devices that share the same unlock authority by design; it does not enable debug unlock on devices outside that set. This issue affects Core ROM: 2.0.0 through 2.0.2, 2.1.0 through 2.1.1; Core Firmware: 2.0.0 through 2.0.1, 2.1.0.
Affected products2
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- Caliptra · Core ROMfrom 2.0.0 up to and including 2.0.2; from 2.1.0 up to and including 2.1.1
- Caliptra · Core Firmwarefrom 2.0.0 up to and including 2.0.1; 2.1.0
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- Caliptra
- Published
- August 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-11836 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.