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.
Published: 2026-08-04
Score: 1.8 Low
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

Insufficient verification in Caliptra Core ROM and Core Firmware's validate_debug_unlock_token() allows a token issued for one device to unlock production debug on another device that shares the same unlock authority key hash. The 384‑bit challenge nonce still blocks replay attacks, but the vulnerability removes the per-device binding that should restrict debug unlock to the intended device.

Affected Systems

Affected vendor Caliptra includes the Core ROM and Core Firmware products. Core ROM versions 2.0.0 through 2.0.2 and 2.1.0 through 2.1.1 are impacted, as are Core Firmware versions 2.0.0 through 2.0.1 and 2.1.0.

Risk and Exploitability

The CVSS score of 1.8 indicates a low severity vulnerability, and the EPSS score is not available while it is not in the CISA KEV catalog. The likely attack vector requires an attacker to have access to the integrator's debug unlock signing service, enabling the issuance of a valid token for a target device. This bypass only affects devices that share the same unlock authority key and does not extend to devices outside that set, so the overall risk to broader systems remains limited.

Generated by OpenCVE AI on August 4, 2026 at 09:27 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Caliptra Core ROM and Core Firmware to a non‑affected version (e.g., a release newer than 2.1.1 for ROM and 2.1.0 for Firmware if available).
  • Restrict and monitor access to the integrator's debug unlock signing service, ensuring only authorized personnel can issue tokens.
  • Verify that debug unlock tokens are bound to an explicit device identifier; if the current implementation lacks this check, implement an additional validation step that rejects tokens not matching the target device.
  • As a temporary measure, disable production debug unlock functionality on devices that are not actively being debugged until the patch can be applied.

Generated by OpenCVE AI on August 4, 2026 at 09:27 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

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

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


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

{'score': 1.8, 'vector': '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'}


Subscriptions

Caliptra Core Firmware Core Rom
cve-icon MITRE

Status: PUBLISHED

Assigner: Caliptra

Published:

Updated: 2026-08-04T21:25:29.941Z

Reserved: 2026-06-09T23:30:40.399Z

Link: CVE-2026-11836

cve-icon Vulnrichment

Updated: 2026-08-04T19:25:07.855Z

cve-icon NVD

Status : Received

Published: 2026-08-04T00:16:40.203

Modified: 2026-08-04T20:16:48.530

Link: CVE-2026-11836

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-07T11:13:27Z

Weaknesses
  • CWE-345

    Insufficient Verification of Data Authenticity