What happened
Microsoft's November 2026 Patch Tuesday (10 November) fixes CVE-2026-119958, a remote code execution flaw in Windows LDAP, the directory protocol that Active Directory runs on. Microsoft rates it Critical, with a CVSS 3.1 score of 9.8.
The bug is an out-of-bounds write (CWE-787). Microsoft's FAQ describes the attack in one sentence: an unauthenticated attacker "could gain code execution through a specially crafted set of LDAP calls to execute arbitrary code within the context of the LDAP service".
- No account is needed.
- No user interaction is needed.
- The attacker only needs network access to the target's LDAP service.
The flaw was reported by Arjun Vasudeva of MSRC V&M, Microsoft's own vulnerability research team.
Why domain controllers come first
On a domain controller, the LDAP service is Active Directory itself. Code running in that context sits at the heart of the domain: accounts, groups, Group Policy and credentials. The Register notes that crafted LDAP requests could end up "potentially compromising domain controllers".
Dustin Childs of Trend Micro's Zero Day Initiative gives the same priority for the whole month: "patch Exchange and Domain Controllers (LDAP/Kerberos) first".
The fix is not limited to servers. Microsoft lists every supported Windows version as affected, workstations included:
| Windows | Fixed build | Update |
|---|---|---|
| Server 2025 | 10.0.26100.33822 | KB5131077 / KB5131080 |
| Server 2022 | 10.0.20348.5870 | KB5131090 |
| Server 2019, Windows 10 1809 | 10.0.17763.9487 | KB5131085 |
| Server 2016, Windows 10 1607 | 10.0.14393.9688 | KB5131291 |
| Windows 10 21H2 / 22H2 | 10.0.19044.7846 / 10.0.19045.7846 | KB5131096 |
| Windows 11 23H2 | 10.0.22631.7711 | KB5131087 |
| Windows 11 24H2 / 25H2 / 26H2 | 10.0.26100.9974 / 10.0.26200.9974 / 10.0.26300.9974 | KB5132043 / KB5132061 |
| Windows 11 26H1 | 10.0.28000.3501 | KB5132059 |
Server Core installations are affected too.
Exploitation status
Microsoft marks the flaw as not exploited and not publicly disclosed, and rates it "Exploitation Less Likely". CISA's assessment in the CVE record is "Exploitation: none", but also "Automatable: yes" and "Technical Impact: total". The CVE is not in CISA's KEV catalog.
"Less likely" is a prediction, not a guarantee. The patch itself shows attackers where the bug is, and patch diffing usually starts within days of Patch Tuesday.
The rest of November's Patch Tuesday
November is a very large release: about 1,100 CVEs according to Talos and The Register (counts differ between sources). The only flaw exploited in the wild is CVE-2026-124194, an Outlook spoofing bug that leaks the user's NTLMv2 hash. Other critical items include:
- CVE-2026-116928, Windows Search remote code execution, also CVSS 9.8;
- CVE-2026-119952, a Schannel remote code execution that Microsoft considers more likely to be exploited;
- CVE-2026-118146, Active Directory Domain Services remote code execution, CVSS 8.8.
What to do
- Patch domain controllers first, then every other Windows server, then workstations. Check the build after the reboot (
winver, or[System.Environment]::OSVersion.Versionin PowerShell). - Microsoft lists no workaround. LDAP cannot be turned off on a domain controller without breaking the domain.
- Until every DC is patched, reduce who can reach LDAP: ports 389 and 636 (and 3268 and 3269 for the Global Catalog) should never be reachable from the internet, guest networks or untrusted segments. This is standard hygiene, not a Microsoft mitigation.
- Watch your DCs for crashes or restarts of
lsass.exe, which hosts the LDAP service. No indicators of compromise have been published.