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 69× in last 7d / 379× 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 769 total refreshes for this CVE.
- 2026-07-28 10:45 UTCVendor advisory
- 2026-07-28 10:45 UTCGHSA enrichment
- 2026-07-28 06:46 UTCVendor advisory
- 2026-07-28 06:46 UTCGHSA enrichment
- 2026-07-28 02:45 UTCVendor advisory
- 2026-07-28 02:45 UTCGHSA enrichment
- 2026-07-27 22:47 UTCVendor advisory
- 2026-07-27 22:47 UTCGHSA enrichment
- 2026-07-27 19:24 UTCCISA KEV update
- 2026-07-27 18:47 UTCVendor advisory
- 2026-07-27 18:47 UTCGHSA enrichment
- 2026-07-27 17:17 UTCCISA KEV update
- 2026-07-27 14:48 UTCVendor advisory
- 2026-07-27 14:48 UTCGHSA enrichment
- 2026-07-27 09:46 UTCVendor advisory
- 2026-07-27 09:46 UTCGHSA enrichment
- 2026-07-27 05:48 UTCVendor advisory
- 2026-07-27 05:48 UTCGHSA enrichment
- 2026-07-27 01:48 UTCVendor advisory
- 2026-07-27 01:48 UTCGHSA enrichment
- 2026-07-26 21:48 UTCVendor advisory
- 2026-07-26 21:48 UTCGHSA enrichment
- 2026-07-26 17:48 UTCEG score recompute
- 2026-07-26 17:48 UTCVendor advisory
- 2026-07-26 17:48 UTCGHSA enrichment
Show 75 moreShow fewer
- 2026-07-26 14:53 UTCEPSS rescore
- 2026-07-26 13:49 UTCEG score recompute
- 2026-07-26 13:49 UTCVendor advisory
- 2026-07-26 13:49 UTCGHSA enrichment
- 2026-07-26 09:51 UTCVendor advisory
- 2026-07-26 09:51 UTCGHSA enrichment
- 2026-07-26 05:52 UTCVendor advisory
- 2026-07-26 05:52 UTCGHSA enrichment
- 2026-07-26 01:53 UTCEG score recompute
- 2026-07-26 01:53 UTCVendor advisory
- 2026-07-26 01:52 UTCGHSA enrichment
- 2026-07-25 14:16 UTCEPSS rescore
- 2026-07-24 14:16 UTCEPSS rescore
- 2026-07-23 14:17 UTCEPSS rescore
- 2026-07-23 14:17 UTCEPSS rescore
- 2026-07-23 02:38 UTCEG score recompute
- 2026-07-22 23:33 UTCEG score recompute
- 2026-07-22 23:33 UTCVendor advisory
- 2026-07-22 23:33 UTCGHSA enrichment
- 2026-07-22 19:40 UTCCISA KEV update
- 2026-07-22 19:34 UTCGHSA enrichment
- 2026-07-22 15:35 UTCEG score recompute
- 2026-07-22 15:35 UTCVendor advisory
- 2026-07-22 15:35 UTCGHSA enrichment
- 2026-07-22 14:07 UTCEPSS rescore
- 2026-07-22 14:07 UTCEPSS rescore
- 2026-07-22 11:36 UTCVendor advisory
- 2026-07-22 11:36 UTCGHSA enrichment
- 2026-07-22 07:35 UTCVendor advisory
- 2026-07-22 07:35 UTCGHSA enrichment
- 2026-07-22 03:36 UTCVendor advisory
- 2026-07-22 03:36 UTCGHSA enrichment
- 2026-07-21 23:37 UTCVendor advisory
- 2026-07-21 23:37 UTCGHSA enrichment
- 2026-07-21 19:37 UTCVendor advisory
- 2026-07-21 19:37 UTCGHSA enrichment
- 2026-07-21 15:36 UTCEG score recompute
- 2026-07-21 15:36 UTCVendor advisory
- 2026-07-21 15:36 UTCGHSA enrichment
- 2026-07-21 15:23 UTCEPSS rescore
- 2026-07-21 15:23 UTCEPSS rescore
- 2026-07-21 14:37 UTCCISA KEV update
- 2026-07-21 11:38 UTCVendor advisory
- 2026-07-21 11:37 UTCGHSA enrichment
- 2026-07-21 07:38 UTCVendor advisory
- 2026-07-21 07:38 UTCGHSA enrichment
- 2026-07-21 03:39 UTCVendor advisory
- 2026-07-21 03:39 UTCGHSA enrichment
- 2026-07-20 23:40 UTCVendor advisory
- 2026-07-20 23:40 UTCGHSA enrichment
- 2026-07-20 19:42 UTCEG score recompute
- 2026-07-20 19:42 UTCVendor advisory
- 2026-07-20 19:42 UTCGHSA enrichment
- 2026-07-20 17:06 UTCEPSS rescore
- 2026-07-20 15:43 UTCGHSA enrichment
- 2026-07-20 11:44 UTCGHSA enrichment
- 2026-07-20 07:45 UTCVendor advisory
- 2026-07-20 07:45 UTCGHSA enrichment
- 2026-07-20 03:45 UTCVendor advisory
- 2026-07-20 03:45 UTCGHSA enrichment
- 2026-07-19 23:46 UTCVendor advisory
- 2026-07-19 23:46 UTCGHSA enrichment
- 2026-07-19 19:48 UTCVendor advisory
- 2026-07-19 19:48 UTCGHSA enrichment
- 2026-07-19 15:49 UTCEG score recompute
- 2026-07-19 15:49 UTCVendor advisory
- 2026-07-19 15:49 UTCGHSA enrichment
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-19 11:51 UTCVendor advisory
- 2026-07-19 11:51 UTCGHSA enrichment
- 2026-07-19 07:52 UTCVendor advisory
- 2026-07-19 07:52 UTCGHSA enrichment
- 2026-07-19 03:52 UTCEG score recompute
- 2026-07-19 03:52 UTCVendor advisory
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 vendor + same CWE)
Same vendor
10 shownmsrc
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.