CVE-2026-9266

HIGHPre-NVD 7.07.0—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 100% 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: epss, secondary
7.0EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: <0.1%CVSS: 7.0Exploit: None knownExposed services: Not assessed

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

A Missing Required Cryptographic Step vulnerability has been identified in Moxa's embedded Linux firmware for industrial computers and controllers. This vulnerability represents an incomplete remediation of CVE-2026-0714. The firmware introduced TPM2 parameter encryption as a countermeasure against CVE-2026-0714. However, an omission in the authorization session configuration causes the parameter encryption to provide no effective protection. An attacker with invasive physical access to the device can still capture TPM communications on the SPI bus and derive the LUKS disk encryption key in plaintext. While successful exploitation results in full compromise of the encrypted disk volume, the attack requires invasive physical access, including opening the device and attaching external equipment to the SPI bus. Remote exploitation is not possible, and the attack does not affect any downstream systems.

CVSS v3
7.0
EG Score
7.0HIGHmedium confidence
EG Risk
36
EG Risk 36/100

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
Severity70% × 45%
Exploitation0% × 40%
Automatability30% × 15%
EPSS PROB
<0.1%
EPSS %ILE
below the 1st
KEV
Not listed

Published

June 12, 2026

Last Modified

June 12, 2026

Advisory Details (1)

Auto-updated Jun 12, 2026
No fix on record yet.

Vendor Advisories for CVE-2026-9266(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 21× 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.

Showing the most recent 100 of 178 total refreshes for this CVE.

  1. 2026-10-08 17:14 UTCEPSS rescore
  2. 2026-10-07 23:48 UTCEPSS rescore
  3. 2026-10-06 15:19 UTCEPSS rescore
  4. 2026-10-05 17:44 UTCEPSS rescore
  5. 2026-10-03 14:26 UTCEPSS rescore
  6. 2026-10-01 19:51 UTCEPSS rescore
  7. 2026-09-30 15:04 UTCEPSS rescore
  8. 2026-09-28 13:52 UTCEPSS rescore
  9. 2026-09-28 13:52 UTCEPSS rescore
  10. 2026-09-26 15:59 UTCEPSS rescore
  11. 2026-09-24 14:04 UTCEPSS rescore
  12. 2026-09-23 17:54 UTCEPSS rescore
  13. 2026-09-22 16:01 UTCEPSS rescore
  14. 2026-09-21 21:09 UTCEPSS rescore
  15. 2026-09-18 19:28 UTCEPSS rescore
  16. 2026-09-17 19:32 UTCEPSS rescore
  17. 2026-09-16 14:09 UTCEPSS rescore
  18. 2026-09-15 03:12 UTCEPSS rescore
  19. 2026-09-14 04:04 UTCEG score recompute
  20. 2026-09-14 04:04 UTCGHSA enrichment
  21. 2026-09-11 14:53 UTCEPSS rescore
  22. 2026-09-10 09:35 UTCEPSS rescore
  23. 2026-09-06 13:48 UTCEPSS rescore
  24. 2026-08-30 23:47 UTCEG score recompute
  25. 2026-08-30 23:47 UTCGHSA enrichment
Show 75 more
  1. 2026-08-25 13:49 UTCEPSS rescore
  2. 2026-08-24 23:51 UTCEG score recompute
  3. 2026-08-24 23:51 UTCGHSA enrichment
  4. 2026-08-24 14:18 UTCEPSS rescore
  5. 2026-08-23 22:29 UTCGHSA enrichment
  6. 2026-08-23 10:37 UTCEG score recompute
  7. 2026-08-23 10:37 UTCGHSA enrichment
  8. 2026-08-23 00:19 UTCEPSS rescore
  9. 2026-08-21 19:32 UTCGHSA enrichment
  10. 2026-08-21 07:55 UTCGHSA enrichment
  11. 2026-08-20 20:27 UTCGHSA enrichment
  12. 2026-08-20 08:47 UTCEG score recompute
  13. 2026-08-20 08:47 UTCGHSA enrichment
  14. 2026-08-19 17:04 UTCEPSS rescore
  15. 2026-08-19 13:45 UTCGHSA enrichment
  16. 2026-08-17 10:20 UTCGHSA enrichment
  17. 2026-08-16 22:53 UTCGHSA enrichment
  18. 2026-08-16 11:07 UTCGHSA enrichment
  19. 2026-08-15 23:40 UTCGHSA enrichment
  20. 2026-08-15 10:35 UTCGHSA enrichment
  21. 2026-08-14 21:50 UTCGHSA enrichment
  22. 2026-08-14 10:23 UTCGHSA enrichment
  23. 2026-08-13 22:55 UTCEG score recompute
  24. 2026-08-13 22:55 UTCGHSA enrichment
  25. 2026-08-13 11:27 UTCGHSA enrichment
  26. 2026-08-12 23:59 UTCGHSA enrichment
  27. 2026-08-12 12:32 UTCGHSA enrichment
  28. 2026-08-12 01:02 UTCGHSA enrichment
  29. 2026-08-11 13:35 UTCGHSA enrichment
  30. 2026-08-11 02:07 UTCGHSA enrichment
  31. 2026-08-10 14:40 UTCGHSA enrichment
  32. 2026-08-10 03:05 UTCGHSA enrichment
  33. 2026-08-09 15:37 UTCGHSA enrichment
  34. 2026-08-09 04:10 UTCGHSA enrichment
  35. 2026-08-08 16:43 UTCGHSA enrichment
  36. 2026-08-08 05:13 UTCGHSA enrichment
  37. 2026-08-07 17:46 UTCGHSA enrichment
  38. 2026-08-07 06:18 UTCGHSA enrichment
  39. 2026-08-06 18:51 UTCEG score recompute
  40. 2026-08-06 18:51 UTCGHSA enrichment
  41. 2026-08-06 13:47 UTCEPSS rescore
  42. 2026-08-06 07:23 UTCGHSA enrichment
  43. 2026-08-05 19:56 UTCEG score recompute
  44. 2026-08-05 19:56 UTCGHSA enrichment
  45. 2026-08-05 19:17 UTCEPSS rescore
  46. 2026-08-05 19:17 UTCEPSS rescore
  47. 2026-08-04 15:47 UTCGHSA enrichment
  48. 2026-08-03 21:28 UTCGHSA enrichment
  49. 2026-08-03 10:00 UTCGHSA enrichment
  50. 2026-08-02 19:44 UTCGHSA enrichment
  51. 2026-08-02 08:16 UTCEG score recompute
  52. 2026-08-02 08:16 UTCGHSA enrichment
  53. 2026-08-02 02:27 UTCEPSS rescore
  54. 2026-08-01 20:48 UTCGHSA enrichment
  55. 2026-08-01 09:19 UTCEG score recompute
  56. 2026-08-01 09:19 UTCGHSA enrichment
  57. 2026-08-01 04:16 UTCEPSS rescore
  58. 2026-07-31 13:33 UTCGHSA enrichment
  59. 2026-07-31 00:34 UTCGHSA enrichment
  60. 2026-07-30 09:27 UTCEG score recompute
  61. 2026-07-30 09:27 UTCGHSA enrichment
  62. 2026-07-30 01:30 UTCEPSS rescore
  63. 2026-07-29 15:51 UTCGHSA enrichment
  64. 2026-07-29 04:23 UTCGHSA enrichment
  65. 2026-07-28 02:08 UTCGHSA enrichment
  66. 2026-07-27 08:11 UTCGHSA enrichment
  67. 2026-07-26 20:43 UTCEG score recompute
  68. 2026-07-26 20:43 UTCGHSA enrichment
  69. 2026-07-26 14:54 UTCEPSS rescore
  70. 2026-07-24 14:18 UTCEPSS rescore
  71. 2026-07-23 03:23 UTCEG score recompute
  72. 2026-07-18 10:04 UTCEPSS rescore
  73. 2026-07-16 23:22 UTCGHSA enrichment
  74. 2026-07-16 04:24 UTCGHSA enrichment
  75. 2026-07-15 16:22 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-9266?
CVE-2026-9266 is a high vulnerability published on June 12, 2026. A Missing Required Cryptographic Step vulnerability has been identified in Moxa's embedded Linux firmware for industrial computers and controllers. This vulnerability represents an incomplete remediation of CVE-2026-0714. The firmware introduced TPM2 parameter encryption as a countermeasure against…
When was CVE-2026-9266 disclosed?
CVE-2026-9266 was first published on June 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-9266 actively exploited?
CVE-2026-9266 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a <0.1% probability of exploitation in the next 30 days (below the 1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-9266?
CVE-2026-9266 has a CVSS base score of 7.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-9266?
No fix for CVE-2026-9266 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. The vendor advisories EchelonGraph has for CVE-2026-9266 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-9266?

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