CVE-2026-11836

Production Debug-Unlock Token Verification Missing Device Binding

State: Published
Severity: 1.8 Low
Published: Aug 4, 2026
Updated: Aug 4, 2026
Reserved: Jun 9, 2026

Description

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.

Scores

CVSS	Score	Vector	Source
4.0	1.8 Low	CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N	Caliptra

Weaknesses

CWE-345 Insufficient Verification of Data Authenticity

Affected Products

Product	Versions
Core ROMCaliptra	2.0.0 through 2.0.2Affected 2.0.3Not affected 2.1.0 through 2.1.1Affected 2.1.2Not affected
Core FirmwareCaliptra	2.0.0 through 2.0.1Affected 2.0.2Not affected 2.1.0Affected 2.1.1Not affected

References

https://github.com/chipsalliance/caliptra-sw/security/advisories/GHSA-hw68-jjx4-m376

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.