CVE-2026-11836: Production Debug-Unlock Token Verification Missing Device Binding

Published Aug 4, 2026
·
Updated

Insufficient verification of data authenticity in Caliptra Core ROM and Core Firmware (validatedebugunlocktoken()) 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.

Affected Software

2 affected components
Caliptra Core ROM>=2.0.0<=2.0.2, >=2.1.0<=2.1.1
Caliptra Core Firmware>=2.0.0<=2.0.1, >=2.1.0<=2.1.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Caliptra Core Firmware to a version that resolves this vulnerability.

    Fixed in 2.0.2
  2. Upgrade

    Upgrade Caliptra Core Firmware to a version that resolves this vulnerability.

    Fixed in 2.1.1

Event History

Aug 4, 2026
CVE Published
via MITRE·12:02 AM
Data Sourced
via MITRE·12:02 AM
DescriptionWeakness
Data Sourced
via NVD·12:16 AM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-11836?

CVE-2026-11836 has been assigned a risk rating of 34, indicating a notable security concern.

2

How does CVE-2026-11836 impact Caliptra Core ROM and Core Firmware?

CVE-2026-11836 allows attackers to exploit insufficient verification of debug unlock tokens, potentially compromising device integrity.

3

Who is affected by CVE-2026-11836?

CVE-2026-11836 affects any users or integrators of the Caliptra Core ROM and Core Firmware that rely on the debug unlock feature.

4

What is the recommended action to mitigate CVE-2026-11836?

To mitigate CVE-2026-11836, implement strong controls to restrict access to the debug unlock signing service and ensure thorough token validation.

5

Is there an available patch for CVE-2026-11836?

A patch or update for CVE-2026-11836 should be sought from the developers of Caliptra, as it addresses the authentication weaknesses.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203
CVE-2026-11836 - Production Debug-Unlock Token Verification Missing Device Binding - SecAlerts