CVE-2026-69779

HIGHPre-NVD 7.07.0—
EchelonGraph scoreHIGH confidence

Score 7.0 from GitHub Security Advisory (severity: HIGH) published 2026-09-08. 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.

Time-of-check time-of-use (toctou) race condition in Windows Win32K 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
11%
KEV
Not listed

Published

September 8, 2026

Last Modified

September 18, 2026

Advisory Details (1)

Auto-updated Sep 8, 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-69779

Vendor Advisories for CVE-2026-69779(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 46× in last 7d / 88× 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 20:15 UTCEG score recompute
  2. 2026-09-19 20:15 UTCVendor advisory
  3. 2026-09-19 20:15 UTCGHSA enrichment
  4. 2026-09-19 08:38 UTCVendor advisory
  5. 2026-09-19 08:38 UTCGHSA enrichment
  6. 2026-09-18 20:59 UTCEG score recompute
  7. 2026-09-18 20:59 UTCVendor advisory
  8. 2026-09-18 20:59 UTCGHSA enrichment
  9. 2026-09-18 19:28 UTCEPSS rescore
  10. 2026-09-18 14:08 UTCVendor advisory
  11. 2026-09-18 14:08 UTCGHSA enrichment
  12. 2026-09-18 11:09 UTCVendor advisory
  13. 2026-09-18 11:09 UTCGHSA enrichment
  14. 2026-09-17 23:32 UTCVendor advisory
  15. 2026-09-17 23:31 UTCGHSA enrichment
  16. 2026-09-17 20:09 UTCEG score recompute
  17. 2026-09-17 20:09 UTCVendor advisory
  18. 2026-09-17 20:09 UTCGHSA enrichment
  19. 2026-09-17 09:48 UTCVendor advisory
  20. 2026-09-17 09:48 UTCGHSA enrichment
  21. 2026-09-16 22:11 UTCEG score recompute
  22. 2026-09-16 22:11 UTCVendor advisory
  23. 2026-09-16 22:10 UTCGHSA enrichment
  24. 2026-09-16 14:08 UTCEPSS rescore
  25. 2026-09-16 10:44 UTCEG score recompute
Show 63 more
  1. 2026-09-16 10:44 UTCVendor advisory
  2. 2026-09-16 10:44 UTCGHSA enrichment
  3. 2026-09-16 05:15 UTCEPSS rescore
  4. 2026-09-15 23:00 UTCVendor advisory
  5. 2026-09-15 23:00 UTCGHSA enrichment
  6. 2026-09-15 17:42 UTCVendor advisory
  7. 2026-09-15 17:42 UTCGHSA enrichment
  8. 2026-09-15 10:49 UTCEG score recompute
  9. 2026-09-15 10:49 UTCVendor advisory
  10. 2026-09-15 10:48 UTCGHSA enrichment
  11. 2026-09-14 23:10 UTCVendor advisory
  12. 2026-09-14 23:10 UTCGHSA enrichment
  13. 2026-09-14 17:41 UTCVendor advisory
  14. 2026-09-14 17:41 UTCGHSA enrichment
  15. 2026-09-14 08:52 UTCVendor advisory
  16. 2026-09-14 08:52 UTCGHSA enrichment
  17. 2026-09-13 21:15 UTCEG score recompute
  18. 2026-09-13 21:15 UTCVendor advisory
  19. 2026-09-13 21:15 UTCGHSA enrichment
  20. 2026-09-13 09:37 UTCVendor advisory
  21. 2026-09-13 09:37 UTCGHSA enrichment
  22. 2026-09-12 22:01 UTCEG score recompute
  23. 2026-09-12 22:01 UTCVendor advisory
  24. 2026-09-12 22:01 UTCGHSA enrichment
  25. 2026-09-12 10:24 UTCVendor advisory
  26. 2026-09-12 10:24 UTCGHSA enrichment
  27. 2026-09-11 22:47 UTCVendor advisory
  28. 2026-09-11 22:46 UTCGHSA enrichment
  29. 2026-09-11 20:01 UTCVendor advisory
  30. 2026-09-11 20:01 UTCGHSA enrichment
  31. 2026-09-11 16:49 UTCEG score recompute
  32. 2026-09-11 16:49 UTCVendor advisory
  33. 2026-09-11 16:49 UTCGHSA enrichment
  34. 2026-09-11 14:53 UTCEPSS rescore
  35. 2026-09-11 11:12 UTCEG score recompute
  36. 2026-09-11 11:11 UTCGHSA enrichment
  37. 2026-09-11 09:37 UTCEPSS rescore
  38. 2026-09-10 23:30 UTCGHSA enrichment
  39. 2026-09-10 21:12 UTCGHSA enrichment
  40. 2026-09-10 09:35 UTCEG score recompute
  41. 2026-09-10 09:35 UTCGHSA enrichment
  42. 2026-09-09 21:58 UTCGHSA enrichment
  43. 2026-09-09 19:48 UTCEG score recompute
  44. 2026-09-09 19:48 UTCVendor advisory
  45. 2026-09-09 19:48 UTCGHSA enrichment
  46. 2026-09-09 10:28 UTCEG score recompute
  47. 2026-09-09 10:28 UTCVendor advisory
  48. 2026-09-09 10:28 UTCGHSA enrichment
  49. 2026-09-09 10:16 UTCVendor advisory
  50. 2026-09-09 10:16 UTCGHSA enrichment
  51. 2026-09-09 04:31 UTCVendor advisory
  52. 2026-09-09 04:31 UTCGHSA enrichment
  53. 2026-09-09 04:05 UTCEG score recompute
  54. 2026-09-09 04:05 UTCVendor advisory
  55. 2026-09-09 04:05 UTCGHSA enrichment
  56. 2026-09-08 23:58 UTCVendor advisory
  57. 2026-09-08 23:58 UTCGHSA enrichment
  58. 2026-09-08 18:43 UTCEG score recompute
  59. 2026-09-08 18:43 UTCVendor advisory
  60. 2026-09-08 18:43 UTCGHSA enrichment
  61. 2026-09-08 17:50 UTCEG score recompute
  62. 2026-09-08 17:50 UTCVendor advisory
  63. 2026-09-08 17:25 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-69779?
CVE-2026-69779 is a high vulnerability published on September 8, 2026. Time-of-check time-of-use (toctou) race condition in Windows Win32K allows an authorized attacker to elevate privileges locally.
When was CVE-2026-69779 disclosed?
CVE-2026-69779 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-69779 actively exploited?
CVE-2026-69779 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.8% of all scored CVEs.
What is the CVSS score of CVE-2026-69779?
CVE-2026-69779 has a CVSS v4.0 base score of 7.0 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-69779?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-69779, 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-69779

Explore →

Is Your Infrastructure Affected by CVE-2026-69779?

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

Start Free Scan →Browse All CVEs