Windows Hyper-V Elevation of Privilege Vulnerability
CVE-2024-38080
Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2024-07-09), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 7.8 retained for reference. Confidence: HIGH.
- Actively exploited in the wild (CISA-KEV)
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.8
- EG Score
- 9.0(high)
- EG Risk
- 81(Attend)EG Risk 81/100SSVC: Attend
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 computedSeverity90% × 45%Exploitation100% × 40%Automatability0% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 7%
- EPSS %ILE
- 94%
- KEV
- ⚠ Exploited
Published
July 9, 2024
Last Modified
October 28, 2025
Advisory Details (2)
Auto-updated Jun 3, 2026Known Exploited Vulnerabilities Catalog | CISA
Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.
https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-38080Security Update Guide - Microsoft Security Response Center
Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-38080Vendor Advisories for CVE-2024-38080(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 102× in last 7d / 422× 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.
Showing the most recent 100 of 1,531 total refreshes for this CVE.
- 2026-09-21 06:27 UTCVendor advisory
- 2026-09-21 06:27 UTCGHSA enrichment
- 2026-09-21 02:28 UTCVendor advisory
- 2026-09-21 02:28 UTCGHSA enrichment
- 2026-09-20 22:29 UTCEG score recompute
- 2026-09-20 22:29 UTCVendor advisory
- 2026-09-20 22:29 UTCGHSA enrichment
- 2026-09-20 20:14 UTCEPSS rescore
- 2026-09-20 20:14 UTCEPSS rescore
- 2026-09-20 18:31 UTCVendor advisory
- 2026-09-20 18:31 UTCGHSA enrichment
- 2026-09-20 14:32 UTCVendor advisory
- 2026-09-20 14:32 UTCGHSA enrichment
- 2026-09-20 10:33 UTCVendor advisory
- 2026-09-20 10:33 UTCGHSA enrichment
- 2026-09-20 06:34 UTCVendor advisory
- 2026-09-20 06:33 UTCGHSA enrichment
- 2026-09-20 06:32 UTCGHSA enrichment
- 2026-09-20 02:30 UTCVendor advisory
- 2026-09-20 02:30 UTCGHSA enrichment
- 2026-09-19 22:31 UTCVendor advisory
- 2026-09-19 22:31 UTCGHSA enrichment
- 2026-09-19 18:33 UTCEG score recompute
- 2026-09-19 18:33 UTCVendor advisory
- 2026-09-19 18:33 UTCGHSA enrichment
Show 75 moreShow fewer
- 2026-09-19 15:40 UTCEPSS rescore
- 2026-09-19 14:34 UTCVendor advisory
- 2026-09-19 14:34 UTCGHSA enrichment
- 2026-09-19 10:35 UTCVendor advisory
- 2026-09-19 10:35 UTCGHSA enrichment
- 2026-09-19 06:31 UTCVendor advisory
- 2026-09-19 06:30 UTCGHSA enrichment
- 2026-09-19 02:31 UTCVendor advisory
- 2026-09-19 02:31 UTCGHSA enrichment
- 2026-09-18 22:33 UTCEG score recompute
- 2026-09-18 22:33 UTCVendor advisory
- 2026-09-18 22:32 UTCGHSA enrichment
- 2026-09-18 19:26 UTCEPSS rescore
- 2026-09-18 19:20 UTCCISA KEV update
- 2026-09-18 18:34 UTCVendor advisory
- 2026-09-18 18:34 UTCGHSA enrichment
- 2026-09-18 14:35 UTCVendor advisory
- 2026-09-18 14:35 UTCGHSA enrichment
- 2026-09-18 14:15 UTCCISA KEV update
- 2026-09-18 10:36 UTCVendor advisory
- 2026-09-18 10:36 UTCGHSA enrichment
- 2026-09-18 06:37 UTCVendor advisory
- 2026-09-18 06:37 UTCGHSA enrichment
- 2026-09-18 02:39 UTCVendor advisory
- 2026-09-18 02:39 UTCGHSA enrichment
- 2026-09-17 22:40 UTCEG score recompute
- 2026-09-17 22:40 UTCVendor advisory
- 2026-09-17 22:40 UTCGHSA enrichment
- 2026-09-17 18:39 UTCVendor advisory
- 2026-09-17 18:39 UTCGHSA enrichment
- 2026-09-17 14:37 UTCVendor advisory
- 2026-09-17 14:37 UTCGHSA enrichment
- 2026-09-17 10:38 UTCVendor advisory
- 2026-09-17 10:38 UTCGHSA enrichment
- 2026-09-17 06:39 UTCVendor advisory
- 2026-09-17 06:38 UTCGHSA enrichment
- 2026-09-17 02:37 UTCVendor advisory
- 2026-09-17 02:37 UTCGHSA enrichment
- 2026-09-16 22:37 UTCVendor advisory
- 2026-09-16 22:37 UTCGHSA enrichment
- 2026-09-16 18:38 UTCVendor advisory
- 2026-09-16 18:38 UTCGHSA enrichment
- 2026-09-16 14:40 UTCEG score recompute
- 2026-09-16 14:40 UTCVendor advisory
- 2026-09-16 14:40 UTCGHSA enrichment
- 2026-09-16 14:10 UTCCISA KEV update
- 2026-09-16 14:06 UTCEPSS rescore
- 2026-09-16 10:41 UTCVendor advisory
- 2026-09-16 10:41 UTCGHSA enrichment
- 2026-09-16 06:37 UTCEG score recompute
- 2026-09-16 06:37 UTCVendor advisory
- 2026-09-16 06:37 UTCGHSA enrichment
- 2026-09-16 02:39 UTCVendor advisory
- 2026-09-16 02:39 UTCGHSA enrichment
- 2026-09-15 22:40 UTCVendor advisory
- 2026-09-15 22:40 UTCGHSA enrichment
- 2026-09-15 18:42 UTCVendor advisory
- 2026-09-15 18:42 UTCGHSA enrichment
- 2026-09-15 14:43 UTCVendor advisory
- 2026-09-15 14:43 UTCGHSA enrichment
- 2026-09-15 10:44 UTCVendor advisory
- 2026-09-15 10:44 UTCGHSA enrichment
- 2026-09-15 06:41 UTCEG score recompute
- 2026-09-15 06:41 UTCVendor advisory
- 2026-09-15 06:41 UTCGHSA enrichment
- 2026-09-15 03:08 UTCEPSS rescore
- 2026-09-15 03:08 UTCEPSS rescore
- 2026-09-15 02:42 UTCGHSA enrichment
- 2026-09-14 22:43 UTCVendor advisory
- 2026-09-14 22:43 UTCGHSA enrichment
- 2026-09-14 19:24 UTCCISA KEV update
- 2026-09-14 18:44 UTCVendor advisory
- 2026-09-14 18:44 UTCGHSA enrichment
- 2026-09-14 14:44 UTCVendor advisory
- 2026-09-14 14:44 UTCGHSA enrichment
Publicly available exploits
(1 reference)Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- GitHub PoCpwndorei/CVE-2024-38080First seen Sep 1, 2024
poc code for CVE-2024-38080
Open source ↗
Related CVEs(same CWE)
Same CWE
10 shownCWE-190
Frequently asked(6)
What is CVE-2024-38080?
When was CVE-2024-38080 disclosed?
Is CVE-2024-38080 actively exploited?
What is the CVSS score of CVE-2024-38080?
Which products are affected by CVE-2024-38080?
How do I remediate CVE-2024-38080?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2024-38080
Is Your Infrastructure Affected by CVE-2024-38080?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.