CVE-2026-20930

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cna:microsoft, epss, ghsa
7.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: 7.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 Management Services allows an authorized attacker to elevate privileges locally.

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

Published

April 14, 2026

Last Modified

August 14, 2026

Advisory Details (1)

Auto-updated Jun 10, 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-20930

Vendor Advisories for CVE-2026-20930(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 5× in last 7d / 24× 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 220 total refreshes for this CVE.

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

Frequently asked(5)

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

Explore →

Is Your Infrastructure Affected by CVE-2026-20930?

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