CVE-2026-72980

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.5 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 67% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 5 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

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

Uncontrolled search path element in Windows Hello allows an authorized attacker to bypass a security feature locally.

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

Published

September 8, 2026

Last Modified

September 18, 2026

Advisory Details (1)

Auto-updated Sep 9, 2026
Patch available. Sources: microsoft.
microsoft Patch Available

Security 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-2026-72980

Vendor Advisories for CVE-2026-72980(2)

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 38× in last 7d / 68× 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 21:37 UTCEG score recompute
  2. 2026-09-19 21:37 UTCVendor advisory
  3. 2026-09-19 21:37 UTCGHSA enrichment
  4. 2026-09-18 20:46 UTCEG score recompute
  5. 2026-09-18 20:46 UTCVendor advisory
  6. 2026-09-18 20:46 UTCGHSA enrichment
  7. 2026-09-18 19:28 UTCEPSS rescore
  8. 2026-09-18 14:14 UTCVendor advisory
  9. 2026-09-18 14:14 UTCGHSA enrichment
  10. 2026-09-18 13:51 UTCVendor advisory
  11. 2026-09-18 13:51 UTCGHSA enrichment
  12. 2026-09-17 23:10 UTCVendor advisory
  13. 2026-09-17 23:10 UTCGHSA enrichment
  14. 2026-09-17 19:56 UTCEG score recompute
  15. 2026-09-17 19:56 UTCVendor advisory
  16. 2026-09-17 19:56 UTCGHSA enrichment
  17. 2026-09-17 19:15 UTCEG score recompute▲ 1.10
  18. 2026-09-17 19:15 UTCVendor advisory
  19. 2026-09-17 19:15 UTCGHSA enrichment
  20. 2026-09-17 19:14 UTCNVD updateCVSS v3 → 5.5
  21. 2026-09-16 22:14 UTCEG score recompute
  22. 2026-09-16 22:14 UTCVendor advisory
  23. 2026-09-16 22:14 UTCGHSA enrichment
  24. 2026-09-16 14:08 UTCEPSS rescore
  25. 2026-09-16 05:15 UTCEPSS rescore
Show 43 more
  1. 2026-09-15 23:08 UTCVendor advisory
  2. 2026-09-15 23:08 UTCGHSA enrichment
  3. 2026-09-15 18:03 UTCEG score recompute
  4. 2026-09-15 18:03 UTCVendor advisory
  5. 2026-09-15 18:03 UTCGHSA enrichment
  6. 2026-09-15 03:12 UTCEPSS rescore
  7. 2026-09-14 23:17 UTCVendor advisory
  8. 2026-09-14 23:17 UTCGHSA enrichment
  9. 2026-09-14 17:52 UTCVendor advisory
  10. 2026-09-14 17:52 UTCGHSA enrichment
  11. 2026-09-14 00:43 UTCEG score recompute
  12. 2026-09-14 00:43 UTCVendor advisory
  13. 2026-09-14 00:43 UTCGHSA enrichment
  14. 2026-09-12 23:53 UTCEG score recompute
  15. 2026-09-12 23:53 UTCVendor advisory
  16. 2026-09-12 23:53 UTCGHSA enrichment
  17. 2026-09-12 15:02 UTCEPSS rescore
  18. 2026-09-11 23:02 UTCVendor advisory
  19. 2026-09-11 23:02 UTCGHSA enrichment
  20. 2026-09-11 19:45 UTCVendor advisory
  21. 2026-09-11 19:45 UTCGHSA enrichment
  22. 2026-09-11 17:06 UTCEG score recompute
  23. 2026-09-11 17:06 UTCVendor advisory
  24. 2026-09-11 17:06 UTCGHSA enrichment
  25. 2026-09-11 14:53 UTCEPSS rescore
  26. 2026-09-10 23:39 UTCEG score recompute
  27. 2026-09-10 23:39 UTCGHSA enrichment
  28. 2026-09-10 15:26 UTCEG score recompute
  29. 2026-09-10 15:26 UTCGHSA enrichment
  30. 2026-09-10 14:36 UTCEG score recompute
  31. 2026-09-10 14:36 UTCGHSA enrichment
  32. 2026-09-10 09:35 UTCEPSS rescore
  33. 2026-09-09 22:32 UTCGHSA enrichment
  34. 2026-09-09 20:13 UTCVendor advisory
  35. 2026-09-09 20:13 UTCGHSA enrichment
  36. 2026-09-09 00:10 UTCEG score recompute
  37. 2026-09-09 00:10 UTCVendor advisory
  38. 2026-09-09 00:10 UTCGHSA enrichment
  39. 2026-09-08 19:04 UTCEG score recompute
  40. 2026-09-08 19:03 UTCGHSA enrichment
  41. 2026-09-08 17:57 UTCEG score recompute
  42. 2026-09-08 17:57 UTCVendor advisory
  43. 2026-09-08 17:25 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-72980?
CVE-2026-72980 is a medium vulnerability published on September 8, 2026. Uncontrolled search path element in Windows Hello allows an authorized attacker to bypass a security feature locally.
When was CVE-2026-72980 disclosed?
CVE-2026-72980 was first published in the National Vulnerability Database on September 8, 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-72980 actively exploited?
CVE-2026-72980 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 67.5% of all scored CVEs.
What is the CVSS score of CVE-2026-72980?
CVE-2026-72980 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-72980?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72980, 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-72980

Explore →

Is Your Infrastructure Affected by CVE-2026-72980?

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

Start Free Scan →Browse All CVEs