CVE-2026-22097

CRITICALPre-NVD 9.39.3—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.3 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 81% 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:divd, epss
Trending — 3 sources updated this week
9.3
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.3Exploit: NoneExposed: 0

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

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.3(medium)
EG Risk
57(Track)
EG Risk 57/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
Severity93% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
18.9%
KEV
Not listed

Published

July 13, 2026

Last Modified

July 16, 2026

Advisory Details (1)

Auto-updated Jul 13, 2026
No patch confirmed yet.
generic

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 14× in last 7d / 43× 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-07-23 14:18 UTCEPSS rescore
  2. 2026-07-23 14:18 UTCEPSS rescore
  3. 2026-07-23 03:06 UTCEG score recompute
  4. 2026-07-22 14:08 UTCEPSS rescore
  5. 2026-07-20 17:08 UTCEPSS rescore
  6. 2026-07-19 14:31 UTCEPSS rescore
  7. 2026-07-19 14:31 UTCEPSS rescore
  8. 2026-07-19 02:29 UTCEPSS rescore
  9. 2026-07-19 02:28 UTCEPSS rescore
  10. 2026-07-18 10:04 UTCEPSS rescore
  11. 2026-07-18 10:04 UTCEPSS rescore
  12. 2026-07-17 05:59 UTCGHSA enrichment
  13. 2026-07-17 01:59 UTCGHSA enrichment
  14. 2026-07-16 21:58 UTCGHSA enrichment
  15. 2026-07-16 17:58 UTCGHSA enrichment
  16. 2026-07-16 17:03 UTCEPSS rescore
  17. 2026-07-16 17:03 UTCEPSS rescore
  18. 2026-07-16 13:58 UTCGHSA enrichment
  19. 2026-07-16 09:56 UTCGHSA enrichment
  20. 2026-07-16 05:56 UTCGHSA enrichment
  21. 2026-07-16 01:57 UTCGHSA enrichment
  22. 2026-07-15 21:57 UTCGHSA enrichment
  23. 2026-07-15 17:57 UTCGHSA enrichment
  24. 2026-07-15 16:57 UTCEPSS rescore
  25. 2026-07-15 16:57 UTCEPSS rescore
Show 18 more
  1. 2026-07-15 13:57 UTCGHSA enrichment
  2. 2026-07-15 09:56 UTCGHSA enrichment
  3. 2026-07-15 05:56 UTCGHSA enrichment
  4. 2026-07-15 02:00 UTCEPSS rescore
  5. 2026-07-15 02:00 UTCEPSS rescore
  6. 2026-07-15 01:55 UTCGHSA enrichment
  7. 2026-07-14 21:55 UTCGHSA enrichment
  8. 2026-07-14 17:55 UTCGHSA enrichment
  9. 2026-07-14 13:53 UTCGHSA enrichment
  10. 2026-07-14 09:53 UTCGHSA enrichment
  11. 2026-07-14 05:53 UTCGHSA enrichment
  12. 2026-07-14 01:53 UTCGHSA enrichment
  13. 2026-07-13 22:30 UTCEPSS rescore
  14. 2026-07-13 21:54 UTCGHSA enrichment
  15. 2026-07-13 17:54 UTCGHSA enrichment
  16. 2026-07-13 13:53 UTCGHSA enrichment
  17. 2026-07-13 09:53 UTCEG score recompute
  18. 2026-07-13 09:52 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-22097?
CVE-2026-22097 is a critical vulnerability 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 CVE-2026-22097 disclosed?
CVE-2026-22097 was first published in the National Vulnerability Database on July 13, 2026, with the most recent update on July 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-22097 actively exploited?
CVE-2026-22097 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 18.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-22097?
CVE-2026-22097 has a CVSS v4.0 base score of 9.3 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-22097?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-22097, 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-22097

Explore →

Is Your Infrastructure Affected by CVE-2026-22097?

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

Start Free Scan →Browse All CVEs