Quick answers
- Is CVE-2026-56188 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-56188 being exploited in the wild.
- How severe is CVE-2026-56188?
- Critical severity, with a CVSS score of 9.8, published 14 July 2026.
- Which products and versions are affected?
- Microsoft Windows 11 24H2, 25H2, 26H1; Microsoft Windows 10 1607, 1809, 21H2, 22H2; Microsoft Windows Server 2012 All editions.
- Is there a fix for CVE-2026-56188?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-56188 attacked?
- It is attacked over the network, in an operating system.
- Am I affected by CVE-2026-56188?
- Check whether you run Microsoft Windows 11, Microsoft Windows 10 or Microsoft Windows Server 2012 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
This vulnerability is classified as a race condition (CWE-362) resulting from improper synchronization during concurrent execution using a shared resource within the Windows Server Network driver. The flaw is exploitable over the network without authentication (AV:N/AC:L/PR:N/UI:N), allowing for remote code execution (RCE). Successful exploitation grants the attacker high confidentiality, integrity, and availability impact, effectively providing full system control. Microsoft has released security updates to address this issue across multiple versions of Windows 10, Windows 11, and Windows Server 2012.
Affected products
- Microsoft Windows 10 1607, 1809, 21H2, 22H2
- Microsoft Windows 11 24H2, 25H2, 26H1
- Microsoft Windows Server 2012 All editions
Timeline
- 2026-07-14: disclosed
- 2026-07-14: advisory