CVE-2026-50349

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.

Concurrent execution using shared resource with improper synchronization ('race condition') in Windows Ancillary Function Driver for WinSock 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
9%
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-50349

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

Frequently asked(5)

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

Explore →

Is Your Infrastructure Affected by CVE-2026-50349?

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