CVE-2026-85921

HIGHPre-NVD 8.28.2—
EchelonGraph scoreHIGH confidence

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

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

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

Double free in Windows Secure Kernel Mode allows an authorized attacker to elevate privileges locally.

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

Published

September 14, 2026

Last Modified

September 18, 2026

Advisory Details (1)

Auto-updated Sep 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-85921

Vendor Advisories for CVE-2026-85921(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.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 61× in last 7d / 61× 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 22:22 UTCEG score recompute
  2. 2026-09-19 22:22 UTCVendor advisory
  3. 2026-09-19 22:22 UTCGHSA enrichment
  4. 2026-09-19 09:43 UTCVendor advisory
  5. 2026-09-19 09:43 UTCGHSA enrichment
  6. 2026-09-18 20:50 UTCEG score recompute
  7. 2026-09-18 20:50 UTCVendor advisory
  8. 2026-09-18 20:50 UTCGHSA enrichment
  9. 2026-09-18 19:28 UTCEPSS rescore
  10. 2026-09-18 14:00 UTCVendor advisory
  11. 2026-09-18 14:00 UTCGHSA enrichment
  12. 2026-09-18 11:45 UTCVendor advisory
  13. 2026-09-18 11:45 UTCGHSA enrichment
  14. 2026-09-17 23:05 UTCVendor advisory
  15. 2026-09-17 23:05 UTCGHSA enrichment
  16. 2026-09-17 20:05 UTCVendor advisory
  17. 2026-09-17 20:05 UTCGHSA enrichment
  18. 2026-09-17 19:54 UTCEG score recompute
  19. 2026-09-17 19:54 UTCVendor advisory
  20. 2026-09-17 19:54 UTCGHSA enrichment
  21. 2026-09-17 19:32 UTCEPSS rescore
  22. 2026-09-17 10:40 UTCVendor advisory
  23. 2026-09-17 10:40 UTCGHSA enrichment
  24. 2026-09-16 22:00 UTCEG score recompute
  25. 2026-09-16 22:00 UTCVendor advisory
Show 36 more
  1. 2026-09-16 22:00 UTCGHSA enrichment
  2. 2026-09-16 19:36 UTCEG score recompute
  3. 2026-09-16 19:36 UTCVendor advisory
  4. 2026-09-16 19:36 UTCGHSA enrichment
  5. 2026-09-16 14:09 UTCEPSS rescore
  6. 2026-09-16 11:26 UTCEG score recompute
  7. 2026-09-16 11:26 UTCVendor advisory
  8. 2026-09-16 11:26 UTCGHSA enrichment
  9. 2026-09-16 05:15 UTCEPSS rescore
  10. 2026-09-15 22:46 UTCVendor advisory
  11. 2026-09-15 22:46 UTCGHSA enrichment
  12. 2026-09-15 17:40 UTCEG score recompute
  13. 2026-09-15 17:40 UTCVendor advisory
  14. 2026-09-15 17:40 UTCGHSA enrichment
  15. 2026-09-15 17:05 UTCVendor advisory
  16. 2026-09-15 17:05 UTCGHSA enrichment
  17. 2026-09-15 04:25 UTCEG score recompute
  18. 2026-09-15 04:25 UTCVendor advisory
  19. 2026-09-15 04:25 UTCGHSA enrichment
  20. 2026-09-15 04:04 UTCVendor advisory
  21. 2026-09-15 04:04 UTCGHSA enrichment
  22. 2026-09-14 22:55 UTCEG score recompute
  23. 2026-09-14 22:55 UTCVendor advisory
  24. 2026-09-14 22:55 UTCGHSA enrichment
  25. 2026-09-14 20:23 UTCEG score recompute
  26. 2026-09-14 20:23 UTCVendor advisory
  27. 2026-09-14 20:23 UTCGHSA enrichment
  28. 2026-09-14 19:30 UTCEG score recompute
  29. 2026-09-14 19:30 UTCVendor advisory
  30. 2026-09-14 19:30 UTCGHSA enrichment
  31. 2026-09-14 18:31 UTCEG score recompute
  32. 2026-09-14 18:31 UTCVendor advisory
  33. 2026-09-14 18:31 UTCGHSA enrichment
  34. 2026-09-14 17:31 UTCEG score recompute
  35. 2026-09-14 17:31 UTCVendor advisory
  36. 2026-09-14 17:30 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-85921?
CVE-2026-85921 is a high vulnerability published on September 14, 2026. Double free in Windows Secure Kernel Mode allows an authorized attacker to elevate privileges locally.
When was CVE-2026-85921 disclosed?
CVE-2026-85921 was first published in the National Vulnerability Database on September 14, 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-85921 actively exploited?
CVE-2026-85921 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 81.7% of all scored CVEs.
What is the CVSS score of CVE-2026-85921?
CVE-2026-85921 has a CVSS v4.0 base score of 8.2 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-85921?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-85921, 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-85921

Explore →

Is Your Infrastructure Affected by CVE-2026-85921?

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

Start Free Scan →Browse All CVEs