CVE-2026-56188

CRITICALNVD 8.19.8▲
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-14. NVD baseline CVSS 8.1; sources differ by 1.7.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 5 sources updated this week
8.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.1Exploit: NoneExposed: 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 Server Network driver allows an unauthorized attacker to execute code over a network.

CVSS v3
8.1
EG Score
9.8(medium)
EG Risk
59(Track)
EG Risk 59/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
Severity98% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
57%
KEV
Not listed

Published

July 14, 2026

Last Modified

July 26, 2026

Advisory Details (1)

Auto-updated Jul 22, 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-56188

Vendor Advisories for CVE-2026-56188(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 22× in last 7d / 64× 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-26 21:49 UTCVendor advisory
  2. 2026-07-26 21:49 UTCGHSA enrichment
  3. 2026-07-26 17:51 UTCVendor advisory
  4. 2026-07-26 17:51 UTCGHSA enrichment
  5. 2026-07-26 15:42 UTCEG score recompute
  6. 2026-07-26 15:42 UTCVendor advisory
  7. 2026-07-26 15:42 UTCGHSA enrichment
  8. 2026-07-26 14:54 UTCEPSS rescore
  9. 2026-07-26 11:44 UTCEG score recompute
  10. 2026-07-26 11:44 UTCVendor advisory
  11. 2026-07-26 11:44 UTCGHSA enrichment
  12. 2026-07-26 04:45 UTCEG score recompute
  13. 2026-07-26 04:45 UTCVendor advisory
  14. 2026-07-26 04:45 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:20 UTCEG score recompute
  19. 2026-07-22 14:08 UTCEPSS rescore
  20. 2026-07-22 13:34 UTCNVD updateCVSS v3 → 8.1 · severity → HIGH
  21. 2026-07-21 15:25 UTCEPSS rescore
  22. 2026-07-20 17:08 UTCEPSS rescore
  23. 2026-07-19 14:31 UTCEPSS rescore
  24. 2026-07-19 14:31 UTCEPSS rescore
  25. 2026-07-19 02:49 UTCEG score recompute
Show 39 more
  1. 2026-07-19 02:49 UTCVendor advisory
  2. 2026-07-19 02:49 UTCGHSA enrichment
  3. 2026-07-19 02:29 UTCEPSS rescore
  4. 2026-07-18 10:04 UTCEPSS rescore
  5. 2026-07-17 05:18 UTCVendor advisory
  6. 2026-07-17 05:18 UTCGHSA enrichment
  7. 2026-07-17 01:20 UTCVendor advisory
  8. 2026-07-17 01:20 UTCGHSA enrichment
  9. 2026-07-16 21:22 UTCVendor advisory
  10. 2026-07-16 21:22 UTCGHSA enrichment
  11. 2026-07-16 17:23 UTCVendor advisory
  12. 2026-07-16 17:23 UTCGHSA enrichment
  13. 2026-07-16 17:03 UTCEPSS rescore
  14. 2026-07-16 13:25 UTCVendor advisory
  15. 2026-07-16 13:24 UTCGHSA enrichment
  16. 2026-07-16 09:25 UTCVendor advisory
  17. 2026-07-16 09:25 UTCGHSA enrichment
  18. 2026-07-16 05:27 UTCVendor advisory
  19. 2026-07-16 05:27 UTCGHSA enrichment
  20. 2026-07-16 01:29 UTCVendor advisory
  21. 2026-07-16 01:29 UTCGHSA enrichment
  22. 2026-07-15 21:31 UTCVendor advisory
  23. 2026-07-15 21:31 UTCGHSA enrichment
  24. 2026-07-15 17:33 UTCVendor advisory
  25. 2026-07-15 17:33 UTCGHSA enrichment
  26. 2026-07-15 16:57 UTCEPSS rescore
  27. 2026-07-15 16:57 UTCEPSS rescore
  28. 2026-07-15 13:35 UTCVendor advisory
  29. 2026-07-15 13:34 UTCGHSA enrichment
  30. 2026-07-15 09:35 UTCVendor advisory
  31. 2026-07-15 09:35 UTCGHSA enrichment
  32. 2026-07-15 05:36 UTCVendor advisory
  33. 2026-07-15 05:36 UTCGHSA enrichment
  34. 2026-07-15 01:38 UTCGHSA enrichment
  35. 2026-07-14 21:40 UTCVendor advisory
  36. 2026-07-14 21:40 UTCGHSA enrichment
  37. 2026-07-14 17:42 UTCEG score recompute
  38. 2026-07-14 17:42 UTCVendor advisory
  39. 2026-07-14 17:40 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-56188?
CVE-2026-56188 is a high vulnerability published on July 14, 2026. Concurrent execution using shared resource with improper synchronization ('race condition') in Windows Server Network driver allows an unauthorized attacker to execute code over a network.
When was CVE-2026-56188 disclosed?
CVE-2026-56188 was first published in the National Vulnerability Database on July 14, 2026, with the most recent update on July 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56188 actively exploited?
CVE-2026-56188 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 56.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-56188?
CVE-2026-56188 has a CVSS v3 base score of 8.1 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.8.
How do I remediate CVE-2026-56188?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56188, 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-56188

Explore →

Is Your Infrastructure Affected by CVE-2026-56188?

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

Start Free Scan →Browse All CVEs