CVE-2026-54107

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-14. the CNA's CVSS baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:microsoft, epss, ghsa
Trending — 4 sources updated this week
8.8EG
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.8Exploit: None knownExposed: 0

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

Concurrent execution using shared resource with improper synchronization ('race condition') in Windows Win32K allows an authorized attacker to elevate privileges locally.

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

Published

July 14, 2026

Last Modified

September 17, 2026

Advisory Details (1)

Auto-updated Jul 14, 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-54107

Vendor Advisories for CVE-2026-54107(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 15× in last 7d / 103× 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 305 total refreshes for this CVE.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 10:18 UTCVendor advisory
  3. 2026-09-18 10:18 UTCGHSA enrichment
  4. 2026-09-17 22:29 UTCEG score recompute
  5. 2026-09-17 22:29 UTCVendor advisory
  6. 2026-09-17 22:29 UTCGHSA enrichment
  7. 2026-09-17 19:31 UTCEPSS rescore
  8. 2026-09-16 14:08 UTCEPSS rescore
  9. 2026-09-16 05:15 UTCEPSS rescore
  10. 2026-09-14 11:14 UTCVendor advisory
  11. 2026-09-14 11:14 UTCGHSA enrichment
  12. 2026-09-13 23:26 UTCEG score recompute
  13. 2026-09-13 23:26 UTCVendor advisory
  14. 2026-09-13 23:26 UTCGHSA enrichment
  15. 2026-09-13 16:47 UTCEPSS rescore
  16. 2026-09-13 07:52 UTCEG score recompute
  17. 2026-09-13 07:52 UTCVendor advisory
  18. 2026-09-13 07:52 UTCGHSA enrichment
  19. 2026-09-12 13:32 UTCVendor advisory
  20. 2026-09-12 13:32 UTCGHSA enrichment
  21. 2026-09-12 01:43 UTCEG score recompute
  22. 2026-09-12 01:43 UTCVendor advisory
  23. 2026-09-12 01:43 UTCGHSA enrichment
  24. 2026-09-11 14:53 UTCEPSS rescore
  25. 2026-09-10 09:35 UTCEPSS rescore
Show 75 more
  1. 2026-09-09 22:55 UTCGHSA enrichment
  2. 2026-09-08 22:50 UTCEG score recompute
  3. 2026-09-08 22:50 UTCVendor advisory
  4. 2026-09-08 22:50 UTCGHSA enrichment
  5. 2026-09-08 22:01 UTCEPSS rescore
  6. 2026-09-08 01:41 UTCEG score recompute
  7. 2026-09-08 01:41 UTCVendor advisory
  8. 2026-09-08 01:41 UTCGHSA enrichment
  9. 2026-09-07 16:01 UTCEPSS rescore
  10. 2026-09-06 13:47 UTCEPSS rescore
  11. 2026-09-06 13:45 UTCVendor advisory
  12. 2026-09-06 13:45 UTCGHSA enrichment
  13. 2026-09-05 21:16 UTCEG score recompute
  14. 2026-09-05 21:16 UTCVendor advisory
  15. 2026-09-05 21:16 UTCGHSA enrichment
  16. 2026-09-04 23:23 UTCEG score recompute
  17. 2026-09-04 23:23 UTCVendor advisory
  18. 2026-09-04 23:23 UTCGHSA enrichment
  19. 2026-09-04 05:06 UTCEPSS rescore
  20. 2026-09-02 19:56 UTCEG score recompute
  21. 2026-09-02 19:56 UTCVendor advisory
  22. 2026-09-02 19:56 UTCGHSA enrichment
  23. 2026-09-02 14:12 UTCEPSS rescore
  24. 2026-09-01 13:54 UTCEPSS rescore
  25. 2026-09-01 04:40 UTCEPSS rescore
  26. 2026-08-31 16:12 UTCVendor advisory
  27. 2026-08-31 16:12 UTCGHSA enrichment
  28. 2026-08-31 05:34 UTCEG score recompute
  29. 2026-08-31 05:34 UTCVendor advisory
  30. 2026-08-31 05:34 UTCGHSA enrichment
  31. 2026-08-30 19:17 UTCEPSS rescore
  32. 2026-08-30 17:03 UTCVendor advisory
  33. 2026-08-30 17:03 UTCGHSA enrichment
  34. 2026-08-30 05:15 UTCEG score recompute
  35. 2026-08-30 05:15 UTCVendor advisory
  36. 2026-08-30 05:15 UTCGHSA enrichment
  37. 2026-08-30 01:22 UTCEPSS rescore
  38. 2026-08-28 23:33 UTCEG score recompute
  39. 2026-08-28 23:33 UTCVendor advisory
  40. 2026-08-28 23:32 UTCGHSA enrichment
  41. 2026-08-28 21:41 UTCEPSS rescore
  42. 2026-08-28 01:59 UTCEG score recompute
  43. 2026-08-28 01:59 UTCVendor advisory
  44. 2026-08-28 01:59 UTCGHSA enrichment
  45. 2026-08-27 14:25 UTCEPSS rescore
  46. 2026-08-27 13:30 UTCGHSA enrichment
  47. 2026-08-27 01:34 UTCEG score recompute
  48. 2026-08-27 01:34 UTCVendor advisory
  49. 2026-08-27 01:34 UTCGHSA enrichment
  50. 2026-08-26 14:46 UTCEPSS rescore
  51. 2026-08-26 13:45 UTCVendor advisory
  52. 2026-08-26 13:45 UTCGHSA enrichment
  53. 2026-08-26 01:39 UTCEG score recompute
  54. 2026-08-26 01:39 UTCVendor advisory
  55. 2026-08-26 01:39 UTCGHSA enrichment
  56. 2026-08-25 13:49 UTCEPSS rescore
  57. 2026-08-25 09:14 UTCVendor advisory
  58. 2026-08-25 09:14 UTCGHSA enrichment
  59. 2026-08-24 21:25 UTCVendor advisory
  60. 2026-08-24 21:25 UTCGHSA enrichment
  61. 2026-08-24 19:48 UTCEG score recompute
  62. 2026-08-24 19:48 UTCVendor advisory
  63. 2026-08-24 19:47 UTCGHSA enrichment
  64. 2026-08-24 04:20 UTCVendor advisory
  65. 2026-08-24 04:20 UTCGHSA enrichment
  66. 2026-08-23 16:31 UTCVendor advisory
  67. 2026-08-23 16:31 UTCGHSA enrichment
  68. 2026-08-23 04:43 UTCEG score recompute
  69. 2026-08-23 04:43 UTCVendor advisory
  70. 2026-08-23 04:43 UTCGHSA enrichment
  71. 2026-08-23 00:19 UTCEPSS rescore
  72. 2026-08-22 16:54 UTCVendor advisory
  73. 2026-08-22 16:54 UTCGHSA enrichment
  74. 2026-08-22 04:46 UTCEG score recompute
  75. 2026-08-22 04:46 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-54107?
CVE-2026-54107 is a high vulnerability published on July 14, 2026. Concurrent execution using shared resource with improper synchronization ('race condition') in Windows Win32K allows an authorized attacker to elevate privileges locally.
When was CVE-2026-54107 disclosed?
CVE-2026-54107 was first published in the National Vulnerability Database on July 14, 2026, with the most recent update on September 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54107 actively exploited?
CVE-2026-54107 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 88.0% of all scored CVEs.
What is the CVSS score of CVE-2026-54107?
CVE-2026-54107 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-54107?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54107, 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-54107

Explore →

Is Your Infrastructure Affected by CVE-2026-54107?

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