CVE-2026-11836 in Core ROM
Summary
by MITRE • 08/04/2026
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.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Analysis
by VulDB Data Team • 08/04/2026
The vulnerability described represents a critical flaw in the authentication mechanism of Caliptra's core firmware components, specifically within the validate_debug_unlock_token() function that operates in subsystem mode. This issue stems from insufficient verification of data authenticity during the debug unlock process, creating a scenario where an attacker with access to the integrator's debug unlock signing service can exploit the system by presenting a valid token issued for a different device that shares the same debug unlock key hash. The flaw resides in the failure to properly validate device-specific identifiers during token validation, allowing cross-device token reuse within a group of devices that share identical unlock authority by design.
The technical implementation of this vulnerability manifests in the absence of proper device-specific authentication checks during the debug unlock token validation process. While the system correctly implements a 384-bit challenge nonce to prevent replay attacks, this protection mechanism is insufficient to address the core issue of device scope enforcement. The challenge nonce effectively prevents attackers from reusing previously issued tokens, but it does not prevent an attacker from obtaining a valid token for one device and then using that same token to unlock debug capabilities on another device within the same set of devices sharing the same debug unlock key hash. This represents a failure in the principle of least privilege and proper access control enforcement.
From an operational perspective, this vulnerability significantly impacts the security posture of embedded systems utilizing Caliptra firmware versions 2.0.0 through 2.0.2, 2.1.0 through 2.1.1 for both Core ROM and Core Firmware components. The practical impact is limited to loss of per-device scope enforcement within a specific set of devices that share the same unlock authority, meaning debug unlock capabilities can be activated on unintended devices within that group. However, this limitation prevents attackers from unlocking devices outside the shared key hash set, which provides some boundary protection. The vulnerability aligns with CWE-287 (Improper Authentication) and represents a variant of privilege escalation through improper access control validation.
The attack vector requires an attacker to have access to the integrator's debug unlock signing service, which constitutes a significant security assumption breach in properly configured systems. This scenario typically occurs when organizations fail to adequately secure their debugging infrastructure or when proper key management practices are not implemented across device fleets. The vulnerability demonstrates weaknesses in the system's authorization model and highlights the importance of implementing proper device-specific authentication checks even when sharing common cryptographic keys across device groups.
Mitigation strategies should focus on strengthening the validation mechanism within validate_debug_unlock_token() to include proper device identification verification before granting debug unlock privileges. Organizations should implement enhanced key management practices that prevent sharing of debug unlock keys across device sets where per-device security is required. The recommended solution involves adding device-specific identifiers to the token validation process, ensuring that tokens can only be used on the specific device for which they were issued. This approach aligns with ATT&CK technique T1548.003 (Abuse Elevation Control Mechanism) and addresses fundamental flaws in access control enforcement mechanisms.
Security teams should conduct comprehensive assessments of their Caliptra firmware deployments to identify affected versions and implement proper device-specific authentication measures. The vulnerability underscores the importance of proper key rotation practices, secure debugging infrastructure management, and adherence to security best practices for embedded systems. Organizations should also consider implementing additional monitoring and logging mechanisms around debug unlock operations to detect potential exploitation attempts. This issue serves as a reminder that even when cryptographic protections are properly implemented, insufficient validation of device context can lead to significant security implications in embedded system environments.