CVE-2026-11836 Overview
CVE-2026-11836 is an authenticity verification weakness [CWE-345] in the Caliptra Core Read-Only Memory (ROM) and Core Firmware. The flaw resides in the validate_debug_unlock_token() routine used in subsystem mode. An attacker with access to an integrator's debug unlock signing service can present a valid token issued for a different device that shares the same debug unlock key hash. The 384-bit challenge nonce still blocks replay of previously issued tokens. The practical impact is loss of per-device scope enforcement across devices that share the same unlock authority by design.
Critical Impact
Production debug can be enabled on an unintended device within a set of parts sharing a common debug unlock key hash, undermining per-device debug scope enforcement.
Affected Products
- Caliptra Core ROM: 2.0.0 through 2.0.2
- Caliptra Core ROM: 2.1.0 through 2.1.1
- Caliptra Core Firmware: 2.0.0 through 2.0.1, and 2.1.0
Discovery Timeline
- 2026-08-04 - CVE-2026-11836 published to the National Vulnerability Database (NVD)
- 2026-08-04 - Last updated in NVD database
Technical Details for CVE-2026-11836
Vulnerability Analysis
Caliptra is an open-source silicon root of trust maintained under the CHIPS Alliance. In subsystem mode, validate_debug_unlock_token() authenticates tokens presented to unlock production debug interfaces. The function verifies the signature against the debug unlock key hash provisioned on the device and checks the 384-bit challenge nonce to prevent replay.
The function does not bind the token to a specific device identity within a group sharing the same unlock key hash. An attacker with access to the integrator's signing service can obtain a legitimate token for one device and present it to another device that trusts the same signer. This transforms a per-device authorization decision into a per-fleet authorization decision.
The impact is bounded. The attacker cannot cross the authority boundary and cannot unlock devices outside the shared-key set. Nonce validation continues to defeat replay of older tokens.
Root Cause
The root cause is insufficient verification of data authenticity [CWE-345]. The token structure and validation logic authenticate the issuer and freshness of the challenge but do not enforce a device-unique identifier binding during signature validation.
Attack Vector
Exploitation requires local access to the target device and high privileges, along with access to the integrator's debug unlock signing service. The attacker requests a valid token for any device in the shared-key set, then presents it to a different device to activate production debug. The mechanism does not require code execution on the target prior to token submission. Refer to the Caliptra GitHub Security Advisory GHSA-hw68-jjx4-m376 for full technical detail.
Detection Methods for CVE-2026-11836
Indicators of Compromise
- Debug unlock token issuance requests from the integrator signing service that do not correlate to an authorized debug session on the intended device identifier.
- Debug mode enablement events on devices that were not scheduled for debug activity.
- Discrepancy between the device identifier a token was issued for and the device identifier that consumed the token.
Detection Strategies
- Audit the integrator debug unlock signing service and correlate every issued token to the exact device identifier that later reports debug activation.
- Monitor Caliptra telemetry and platform logs for validate_debug_unlock_token() acceptance events and compare token metadata against expected device scope.
- Flag any acceptance of a token on a device whose serial or unique identifier does not match the requester context in the signing service ticket.
Monitoring Recommendations
- Enable and centralize logging for all debug unlock ceremonies across manufacturing, RMA, and field engineering workflows.
- Alert on repeated debug unlock requests targeting different devices from the same operator identity within short time windows.
- Review privileged access to the debug unlock signing service on a recurring basis and revoke stale credentials.
How to Mitigate CVE-2026-11836
Immediate Actions Required
- Inventory devices running affected Caliptra Core ROM (2.0.0–2.0.2, 2.1.0–2.1.1) and Core Firmware (2.0.0–2.0.1, 2.1.0).
- Restrict access to the integrator's debug unlock signing service to a minimum set of operators and require ticket-bound approval for each request.
- Treat any device sharing an unlock key hash with a compromised or improperly issued token as within scope for review.
Patch Information
Refer to the vendor advisory at Caliptra GitHub Security Advisory GHSA-hw68-jjx4-m376 for fixed versions and integration guidance. Integrators should update Caliptra Core ROM and Core Firmware to versions containing the corrected token validation logic and re-provision affected devices where required.
Workarounds
- Provision unique debug unlock key hashes per device or per small device group to reduce the blast radius of scope enforcement loss.
- Enforce out-of-band approval and dual control on the signing service so that a single operator cannot request tokens for arbitrary device identifiers.
- Disable production debug capability entirely on devices that do not require field debug access.
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
