# CVE-2026-41089: Windows Netlogon Remote Code Execution Vulnerability

> An unauthorized attacker can execute arbitrary code remotely via a stack-based buffer overflow in the Windows Netlogon service.

- **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:** 12 May 2026
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-7j2c-v44v-wc8f

## What is CVE-2026-41089?

CVE-2026-41089 is a critical memory corruption vulnerability in Microsoft Windows Server 2012, published on 12 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Stack-based buffer overflow in Windows Netlogon allows an unauthorized attacker to execute code over a network.

Weakness: CWE-121 (Stack-based Buffer Overflow)

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

It affects 6 products.


Products: Microsoft Windows Server 2012, Microsoft Windows Server 2016, Microsoft Windows Server 2019, Microsoft Windows Server 2022, Microsoft Windows Server 2022 23h2, Microsoft Windows Server 2025.

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

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

## Is CVE-2026-41089 being exploited?

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

Public exploit code:

- Netlogon and CLDAP vulnerability research with a proof of concept. (github_poc): https://github.com/0xABCD01/CVE-2026-41089
- CVE-2026-41089 Netlogon RCE PoC — security research, vulnerability validation & defensive testing. (github_poc): https://github.com/SyntaxMethod/CVE-2026-41089-Netlogon-RCE-PoC
- CVE-2026-41089 checker: unauthenticated, non-destructive detection for the Netlogon CLDAP stack buffer overflow (CVSS 9.8). Reports whether a domain controller's domain is long enough to crash, without sending the overflow. The binary-verified analysis the public PoCs got wrong. (github_poc): https://github.com/ADScanPro/CVE-2026-41089-LongLogon
- CVE-2026-41089 (github_poc): https://github.com/0xredash/CVE-2026-41089
- 🛡️ Official AI Security Tool diagnostic module for CVE-2026-41089 (Windows Netlogon Stack Buffer Overflow RCE). Features technical writeup, attack architecture, IoCs, and mitigation strategy. (github_poc): https://github.com/ZeroDayVPN/CVE-2026-41089-Netlogon
- Automate Netlogon CVE-2026-41089 validation and defensive testing through integrated AI security workflows, enabling rapid risk assessment and mitigation verification. (github_poc): https://github.com/Gillarchnganasan2735/CVE-2026-41089-Netlogon-RCE-PoC

## Other vulnerabilities in Microsoft Windows Server 2012

- [CVE-2025-59287](https://insights.sbomify.com/CVE-2025-59287/): Microsoft Windows Server Update Service (WSUS) Deserialization of Untrusted Data (critical 9.8, exploited in the wild)
- [CVE-2026-69595](https://insights.sbomify.com/CVE-2026-69595/): Windows Services for NFS ONCRPC XDR Driver Remote Code Execution Vulnerability (critical 9.8)
- [CVE-2026-78445](https://insights.sbomify.com/CVE-2026-78445/): Windows Services for NFS ONCRPC XDR Driver Remote Code Execution Vulnerability (critical 9.8)
- [CVE-2024-43639](https://insights.sbomify.com/CVE-2024-43639/): Windows KDC Proxy Remote Code Execution Vulnerability (critical 9.8)
- [CVE-2023-24941](https://insights.sbomify.com/CVE-2023-24941/): Windows Network File System Remote Code Execution Vulnerability (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-41089 is a critical memory corruption vulnerability in Microsoft Windows Server 2012, published on 12 May 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-41089 in the wild and no public exploit code.

Affected product: Microsoft Windows Server 2012. 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-41089/ (Markdown: https://insights.sbomify.com/CVE-2026-41089/index.md)
```

## Sources

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

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