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 — 4 sources updated this week
9.8EG
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: 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 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 28, 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 60× in last 7d / 106× 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 106 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-56188?
CVE-2026-56188 is a critical 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 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-56188 actively exploited?
CVE-2026-56188 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 43.5% of all scored CVEs.
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.