CVE-2026-49806

HIGHPre-NVD 7.07.0
EchelonGraph scoreMEDIUM 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: 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 USB Print Driver allows an authorized attacker to elevate privileges locally.

CVSS v3
7.0
EG Score
7.0(medium)
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
10%
KEV
Not listed

Published

July 14, 2026

Last Modified

August 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-49806

Vendor Advisories for CVE-2026-49806(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 / 166× 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 235 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-49806?
CVE-2026-49806 is a high vulnerability published on July 14, 2026. Concurrent execution using shared resource with improper synchronization ('race condition') in Windows USB Print Driver allows an authorized attacker to elevate privileges locally.
When was CVE-2026-49806 disclosed?
CVE-2026-49806 was first published in the National Vulnerability Database on July 14, 2026, with the most recent update on August 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-49806 actively exploited?
CVE-2026-49806 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 89.9% of all scored CVEs.
What is the CVSS score of CVE-2026-49806?
CVE-2026-49806 has a CVSS v4.0 base score of 7.0 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-49806?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49806, 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-49806

Explore →

Is Your Infrastructure Affected by CVE-2026-49806?

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