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.
Metrics
Affected Vendors & Products
No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Fri, 07 Aug 2026 11:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Caliptra
Caliptra core Firmware Caliptra core Rom |
|
| Vendors & Products |
Caliptra
Caliptra core Firmware Caliptra core Rom |
Tue, 04 Aug 2026 20:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Tue, 04 Aug 2026 00:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Production Debug-Unlock Token Verification Missing Device Binding | |
| Weaknesses | CWE-345 | |
| References |
| |
| Metrics |
cvssV4_0
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: Caliptra
Published:
Updated: 2026-08-04T21:25:29.941Z
Reserved: 2026-06-09T23:30:40.399Z
Link: CVE-2026-11836
Updated: 2026-08-04T19:25:07.855Z
Status : Received
Published: 2026-08-04T00:16:40.203
Modified: 2026-08-04T20:16:48.530
Link: CVE-2026-11836
No data.
OpenCVE Enrichment
Updated: 2026-08-07T11:13:27Z