CVE-2026-80469

HIGHPre-NVD 8.38.3
EchelonGraph scoreHIGH confidence

Score 8.3 from GitHub Security Advisory (severity: HIGH) published 2026-09-11. a secondary CVSS source baseline 8.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.3EG
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.3Exploit: None knownExposed: 0

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

An attacker may achieve arbitrary code execution on a target system by uploading a malicious device driver package, bypassing driver verification mechanisms, and triggering the execution of attacker-controlled code. User interaction is required.

CVSS v3
8.3
EG Score
8.3(high)
EG Risk
37(Track)
EG Risk 37/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
Severity83% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
14%
KEV
Not listed

Published

September 11, 2026

Last Modified

September 18, 2026

Advisory Details (5)

Auto-updated Sep 11, 2026
🔬 Proof of concept available. Patch available. Sources: cisa.

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

Frequently asked(5)

What is CVE-2026-80469?
CVE-2026-80469 is a high vulnerability published on September 11, 2026. An attacker may achieve arbitrary code execution on a target system by uploading a malicious device driver package, bypassing driver verification mechanisms, and triggering the execution of attacker-controlled code. User interaction is required.
When was CVE-2026-80469 disclosed?
CVE-2026-80469 was first published in the National Vulnerability Database on September 11, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-80469 actively exploited?
CVE-2026-80469 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 85.9% of all scored CVEs.
What is the CVSS score of CVE-2026-80469?
CVE-2026-80469 has a CVSS v3 base score of 8.3 (NVD).
How do I remediate CVE-2026-80469?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-80469, 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-80469

Explore →

Is Your Infrastructure Affected by CVE-2026-80469?

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