CVE-2026-0667

CRITICALPre-NVD 9.39.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This critical-severity CVE scores 9.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (43rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week
9.3EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.3Exploit: None knownExposed services: Not assessed

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

CWE-754: Improper Check for Unusual or Exceptional Conditions vulnerability that could cause arbitrary code execution, denial of service and loss of confidentiality & integrity when communicating over the Modbus TCP protocol.

CVSS v3
9.3
EG Score
9.3CRITICALmedium confidence
EG Risk
57
EG Risk 57/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 (value × EchelonGraph’s weight)
Severity93% × 45%
The EG Score, 9.3 of 10.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.5%
EPSS %ILE
43rd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 29, 2026

Last Modified

July 30, 2026

Advisory Details (1)

Auto-updated Oct 8, 2026
No fix on record yet.
Web page
https://download.se.com/files?p_Doc_Ref=SEVD-2026-041-01&p_enDocType=Security+and+Safety+Notice&p_File_Name=SEVD-2026-041-01.pdf

Vendor Advisories for CVE-2026-0667(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 16× in last 7d / 89× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 412 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 312 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-0667?
CVE-2026-0667 is a critical-severity vulnerability; its CVE record was published on July 29, 2026. CWE-754: Improper Check for Unusual or Exceptional Conditions vulnerability that could cause arbitrary code execution, denial of service and loss of confidentiality & integrity when communicating over the Modbus TCP protocol.
When was the CVE record for CVE-2026-0667 published?
The CVE record for CVE-2026-0667 was published on July 29, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 30, 2026; the record at its source may have been updated since.
Is CVE-2026-0667 actively exploited?
CVE-2026-0667 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (43rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-0667?
CVE-2026-0667 has a CVSS base score of 9.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-0667?
No fix for CVE-2026-0667 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-0667 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-0667?

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

Book a Demo →Browse All CVEs