CVE-2026-59126

HIGHPre-NVD 7.07.0
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cna:microsoft, epss, ghsa
Trending — 4 sources updated this week
7.0EG
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.0Exploit: 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 Event Logging Service allows an authorized attacker to elevate privileges locally.

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

Published

August 11, 2026

Last Modified

August 20, 2026

Advisory Details (1)

Auto-updated Aug 11, 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-59126

Vendor Advisories for CVE-2026-59126(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 79× in last 7d / 124× 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 124 total refreshes for this CVE.

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

Frequently asked(5)

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

Explore →

Is Your Infrastructure Affected by CVE-2026-59126?

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