CVE-2026-49805

HIGHPre-NVD 7.07.0—
EchelonGraph scoreHIGH confidence

Score 7.0 from GitHub Security Advisory (severity: HIGH) published 2026-07-14. 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: 3%CVSS: 7.0Exploit: None knownExposed: 0

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

Improper access control in Windows Win32K allows an authorized attacker to elevate privileges locally.

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

Published

July 14, 2026

Last Modified

July 30, 2026

Advisory Details (1)

Auto-updated Jul 15, 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-49805

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

Frequently asked(5)

What is CVE-2026-49805?
CVE-2026-49805 is a high vulnerability published on July 14, 2026. Improper access control in Windows Win32K allows an authorized attacker to elevate privileges locally.
When was CVE-2026-49805 disclosed?
CVE-2026-49805 was first published in the National Vulnerability Database on July 14, 2026, with the most recent update on July 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49805 actively exploited?
CVE-2026-49805 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3% probability of exploitation in the next 30 days, which ranks it in the top 12.7% of all scored CVEs.
What is the CVSS score of CVE-2026-49805?
CVE-2026-49805 has a CVSS v4.0 base score of 7.0 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-49805?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49805, 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-49805

Explore →

Is Your Infrastructure Affected by CVE-2026-49805?

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

Start Free Scan →Browse All CVEs