# CVE-2026-56188: Windows Server Network driver Remote Code Execution Vulnerability

> An unauthorized attacker can execute code over a network due to a race condition in the Windows Server Network driver.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jul 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-fw6g-55xx-prrm

## What is CVE-2026-56188?

CVE-2026-56188 is a critical vulnerability in Microsoft Windows 10 1607, published on 14 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2026-56188?

It affects 12 products.


Products: Microsoft Windows 10 1607, Microsoft Windows 10 1809, Microsoft Windows 10 21h2, Microsoft Windows 10 22h2, Microsoft Windows 11 24h2, Microsoft Windows 11 25h2, Microsoft Windows 11 26h1, Microsoft Windows Server 2012, Microsoft Windows Server 2016, Microsoft Windows Server 2019, Microsoft Windows Server 2022, Microsoft Windows Server 2025.

## How do I fix CVE-2026-56188?

No fix has been published for CVE-2026-56188 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-56188 being exploited?

There is no known exploitation of CVE-2026-56188 in the wild and no public exploit code.

## Other vulnerabilities in Microsoft Windows 10 1607

- [CVE-2026-33824](https://insights.sbomify.com/CVE-2026-33824/): Microsoft Internet Key Exchange (IKE) Service Extensions Double Free (critical 9.8, exploited in the wild)
- [CVE-2026-21510](https://insights.sbomify.com/CVE-2026-21510/): Microsoft Windows Shell Protection Mechanism Failure (high 8.8, exploited in the wild)
- [CVE-2026-21513](https://insights.sbomify.com/CVE-2026-21513/): Microsoft MSHTML Framework Protection Mechanism Failure (high 8.8, exploited in the wild)
- [CVE-2023-32049](https://insights.sbomify.com/CVE-2023-32049/): Microsoft Windows Defender SmartScreen Security Feature Bypass (high 8.8, exploited in the wild)
- [CVE-2023-29360](https://insights.sbomify.com/CVE-2023-29360/): Microsoft Streaming Service Untrusted Pointer Dereference (high 8.4, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-56188 and fix it if it is affected.

What it is: CVE-2026-56188 is a critical vulnerability in Microsoft Windows 10 1607, published on 14 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-56188 in the wild and no public exploit code.

Affected product: Microsoft Windows 10 1607. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-56188/ (Markdown: https://insights.sbomify.com/CVE-2026-56188/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-56188
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-56188
- OSV: https://osv.dev/vulnerability/CVE-2026-56188

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-56188/
Summaries are generated and may contain mistakes; the official description above is the record.