CVE-2026-11836

LOWPre-NVD 1.81.8
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 1.8 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 99% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cna:caliptra, epss
1.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 1.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
1.8
EG Score
1.8(medium)
EG Risk
8(Track)
EG Risk 8/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity18% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

August 4, 2026

Last Modified

August 4, 2026

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 16× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-25 13:48 UTCEPSS rescore
  2. 2026-08-24 20:17 UTCEG score recompute
  3. 2026-08-23 00:19 UTCEPSS rescore
  4. 2026-08-21 23:55 UTCEG score recompute
  5. 2026-08-20 22:55 UTCEPSS rescore
  6. 2026-08-19 17:03 UTCEPSS rescore
  7. 2026-08-13 10:50 UTCEG score recompute
  8. 2026-08-07 18:06 UTCEG score recompute
  9. 2026-08-05 19:17 UTCEPSS rescore
  10. 2026-08-04 21:44 UTCEG score recompute
  11. 2026-08-04 20:33 UTCEG score recompute
  12. 2026-08-04 19:31 UTCEG score recompute
  13. 2026-08-04 15:09 UTCEPSS rescore
  14. 2026-08-04 00:25 UTCEG score recompute
  15. 2026-08-04 00:13 UTCEG score recompute
  16. 2026-08-04 00:13 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-11836?
CVE-2026-11836 is a low vulnerability published on August 4, 2026. Insufficient verification of data authenticity in Caliptra Core ROM and Core Firmware (validatedebugunlock_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…
When was CVE-2026-11836 disclosed?
CVE-2026-11836 was first published in the National Vulnerability Database on August 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-11836 actively exploited?
CVE-2026-11836 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.9% of all scored CVEs.
What is the CVSS score of CVE-2026-11836?
CVE-2026-11836 has a CVSS v4.0 base score of 1.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-11836?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-11836, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-11836

Explore →

Is Your Infrastructure Affected by CVE-2026-11836?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.