CVE-2026-22097

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 the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.3% (25th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from the CNA's CVSS
Sources: the CNA's CVSS, EPSS
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.3%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.

The CVE record's CNA (Dutch Institute for Vulnerability Disclosure (DIVD)) lists EVbee DC-80 versions before 1.5.1 as affected. No release containing a fix is confirmed on record.

The firmware update mechanism does not include cryptographic signature validation. This allows anyone with access to the firmware update capability to upload arbitrary files which can then lead to arbitrary code execution.

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.3% × 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.3%
EPSS %ILE
25th
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 13, 2026

Last Modified

July 16, 2026

Advisory Details (1)

Auto-updated Oct 8, 2026
No fix on record yet.
Web page

Redirecting…

https://csirt.divd.nl/DIVD-2026-00001/

Vendor Advisories for CVE-2026-22097(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 / 44× 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 99 of 375 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 276 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-22097?
CVE-2026-22097 is a critical-severity vulnerability; its CVE record was published on July 13, 2026. The firmware update mechanism does not include cryptographic signature validation. This allows anyone with access to the firmware update capability to upload arbitrary files which can then lead to arbitrary code execution.
When was the CVE record for CVE-2026-22097 published?
The CVE record for CVE-2026-22097 was published on July 13, 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 16, 2026; the record at its source may have been updated since.
Is CVE-2026-22097 actively exploited?
CVE-2026-22097 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (25th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-22097?
CVE-2026-22097 has a CVSS base score of 9.3 (the CNA's own assessment, by divd; NVD's own analysis pending).
How do I remediate CVE-2026-22097?
No fix for CVE-2026-22097 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 CVE record's CNA (Dutch Institute for Vulnerability Disclosure (DIVD)) lists EVbee DC-80 versions before 1.5.1 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-22097 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-22097?

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

Book a Demo →Browse All CVEs