CVE-2026-9140

HIGHPre-NVD 8.78.7
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 83% 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
Trending — 3 sources updated this week
8.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.7Exploit: None knownExposed: 0

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

A denial-of-service security issue exists in the 1719-AENTR. The security issue stems from improper handling of a UDP unicast network storm, which causes the device to become overloaded and lose communication. A power cycle is required to recover.

CVSS v3
8.7
EG Score
8.7(medium)
EG Risk
54(Track)
EG Risk 54/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
Severity87% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
17%
KEV
Not listed

Published

July 14, 2026

Last Modified

July 14, 2026

Advisory Details (1)

Auto-updated Jul 14, 2026
No patch confirmed yet.

Vendor Advisories for CVE-2026-9140(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 18× in last 7d / 34× 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-29 05:52 UTCGHSA enrichment
  2. 2026-07-28 18:55 UTCEG score recompute
  3. 2026-07-28 18:55 UTCGHSA enrichment
  4. 2026-07-28 15:37 UTCEPSS rescore
  5. 2026-07-28 07:52 UTCGHSA enrichment
  6. 2026-07-27 20:52 UTCEG score recompute
  7. 2026-07-27 20:52 UTCGHSA enrichment
  8. 2026-07-27 14:14 UTCEPSS rescore
  9. 2026-07-27 09:38 UTCGHSA enrichment
  10. 2026-07-26 22:43 UTCEG score recompute
  11. 2026-07-26 22:43 UTCGHSA enrichment
  12. 2026-07-26 14:54 UTCEPSS rescore
  13. 2026-07-26 11:47 UTCEG score recompute
  14. 2026-07-26 11:47 UTCGHSA enrichment
  15. 2026-07-25 14:18 UTCEPSS rescore
  16. 2026-07-24 14:18 UTCEPSS rescore
  17. 2026-07-23 14:18 UTCEPSS rescore
  18. 2026-07-23 03:23 UTCEG score recompute
  19. 2026-07-22 14:08 UTCEPSS rescore
  20. 2026-07-21 15:25 UTCEPSS rescore
  21. 2026-07-21 15:25 UTCEPSS rescore
  22. 2026-07-20 17:08 UTCEPSS rescore
  23. 2026-07-19 14:31 UTCEPSS rescore
  24. 2026-07-19 02:29 UTCEPSS rescore
  25. 2026-07-18 10:04 UTCEPSS rescore
Show 9 more
  1. 2026-07-16 21:45 UTCGHSA enrichment
  2. 2026-07-16 17:03 UTCEPSS rescore
  3. 2026-07-16 10:50 UTCGHSA enrichment
  4. 2026-07-15 23:54 UTCGHSA enrichment
  5. 2026-07-15 16:57 UTCEPSS rescore
  6. 2026-07-15 12:58 UTCGHSA enrichment
  7. 2026-07-15 02:02 UTCGHSA enrichment
  8. 2026-07-14 15:06 UTCEG score recompute
  9. 2026-07-14 15:05 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-9140?
CVE-2026-9140 is a high vulnerability published on July 14, 2026. A denial-of-service security issue exists in the 1719-AENTR. The security issue stems from improper handling of a UDP unicast network storm, which causes the device to become overloaded and lose communication. A power cycle is required to recover.
When was CVE-2026-9140 disclosed?
CVE-2026-9140 was first published in the National Vulnerability Database on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-9140 actively exploited?
CVE-2026-9140 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 83.2% of all scored CVEs.
What is the CVSS score of CVE-2026-9140?
CVE-2026-9140 has a CVSS v3 base score of 8.7 (NVD).
How do I remediate CVE-2026-9140?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-9140, 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-9140

Explore →

Is Your Infrastructure Affected by CVE-2026-9140?

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