CVE-2026-49808

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

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

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

CVSS v3
7.8
EG Score
7.8(high)
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
5%
KEV
Not listed

Published

July 14, 2026

Last Modified

July 28, 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-49808

Vendor Advisories for CVE-2026-49808(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

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

Explore →

Is Your Infrastructure Affected by CVE-2026-49808?

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

Start Free Scan →Browse All CVEs