CVE-2026-11836

LOWPre-NVD 1.81.8—
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 1.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1% (1st percentile of EPSS-scored CVEs). 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: epss, secondary
1.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 1.8Exploit: None knownExposed services: Not assessed

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

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.8LOWmedium confidence
EG Risk
8
EG Risk 8/100CISA SSVC

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%
CISA SSVC: Track at every mission impact level.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.1%
EPSS %ILE
1st
KEV
Not listed

CISA SSVCTrack at every mission impact level.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 4, 2026

Last Modified

September 3, 2026

References (1)

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 24× 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-10-10 19:59 UTCEPSS rescore
  2. 2026-10-09 20:06 UTCEPSS rescore
  3. 2026-10-08 17:11 UTCEPSS rescore
  4. 2026-10-07 23:47 UTCEPSS rescore
  5. 2026-10-07 04:01 UTCEG score recompute
  6. 2026-10-06 15:17 UTCEPSS rescore
  7. 2026-10-05 17:42 UTCEPSS rescore
  8. 2026-10-04 23:21 UTCEPSS rescore
  9. 2026-10-04 06:16 UTCEG score recompute
  10. 2026-10-03 14:25 UTCEPSS rescore
  11. 2026-10-01 19:49 UTCEPSS rescore
  12. 2026-10-01 02:30 UTCEG score recompute
  13. 2026-09-30 15:02 UTCEPSS rescore
  14. 2026-09-27 18:12 UTCEG score recompute
  15. 2026-09-26 15:58 UTCEPSS rescore
  16. 2026-09-23 21:23 UTCEG score recompute
  17. 2026-09-20 21:36 UTCEG score recompute
  18. 2026-09-18 19:27 UTCEPSS rescore
  19. 2026-09-18 01:10 UTCEG score recompute
  20. 2026-09-15 02:43 UTCEG score recompute
  21. 2026-09-12 15:00 UTCEPSS rescore
  22. 2026-09-12 06:03 UTCEG score recompute
  23. 2026-09-11 14:52 UTCEPSS rescore
  24. 2026-09-11 09:36 UTCEPSS rescore
  25. 2026-09-10 09:34 UTCEPSS rescore
Show 32 more
  1. 2026-09-09 09:41 UTCEG score recompute
  2. 2026-09-08 22:00 UTCEPSS rescore
  3. 2026-09-07 16:01 UTCEPSS rescore
  4. 2026-09-06 13:47 UTCEPSS rescore
  5. 2026-09-06 13:19 UTCEG score recompute
  6. 2026-09-04 05:06 UTCEPSS rescore
  7. 2026-09-03 16:57 UTCEG score recompute
  8. 2026-09-03 08:24 UTCEG score recompute
  9. 2026-09-02 14:11 UTCEPSS rescore
  10. 2026-09-01 04:39 UTCEPSS rescore
  11. 2026-08-30 19:17 UTCEPSS rescore
  12. 2026-08-30 16:22 UTCEG score recompute
  13. 2026-08-30 01:21 UTCEPSS rescore
  14. 2026-08-28 21:40 UTCEPSS rescore
  15. 2026-08-27 20:00 UTCEG score recompute
  16. 2026-08-27 14:24 UTCEPSS rescore
  17. 2026-08-25 13:48 UTCEPSS rescore
  18. 2026-08-24 20:17 UTCEG score recompute
  19. 2026-08-23 00:19 UTCEPSS rescore
  20. 2026-08-21 23:55 UTCEG score recompute
  21. 2026-08-20 22:55 UTCEPSS rescore
  22. 2026-08-19 17:03 UTCEPSS rescore
  23. 2026-08-13 10:50 UTCEG score recompute
  24. 2026-08-07 18:06 UTCEG score recompute
  25. 2026-08-05 19:17 UTCEPSS rescore
  26. 2026-08-04 21:44 UTCEG score recompute
  27. 2026-08-04 20:33 UTCEG score recompute
  28. 2026-08-04 19:31 UTCEG score recompute
  29. 2026-08-04 15:09 UTCEPSS rescore
  30. 2026-08-04 00:25 UTCEG score recompute
  31. 2026-08-04 00:13 UTCEG score recompute
  32. 2026-08-04 00:13 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

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 on August 4, 2026, with the most recent update on September 3, 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.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-11836?
CVE-2026-11836 has a CVSS base score of 1.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-11836?
No fix for CVE-2026-11836 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix.

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.

Book a Demo →Browse All CVEs