On this page (7 sections)
What was disclosed
CVE-2026-119958 is a critical flaw in the Windows implementation of LDAP, the Lightweight Directory Access Protocol. According to the NVD entry, it is an out-of-bounds write that allows an unauthorized attacker to execute code over a network. The record was published on 2026-11-10 and carries a CVSS score of 9.8.
Anyone who runs Windows servers that speak LDAP, especially domain controllers and directory-integrated services, should treat this as a priority to track. Very little detail is public so far, so this article separates what is confirmed from what is not.
What is confirmed and what is not
The only primary source available is the NVD record, which carries the one-line description. The CVE record also points to the Microsoft Security Response Center update guide as a reference. Only one independent publisher covers this story so far, so there is no second source to corroborate details.
- Confirmed by the record: the component (Windows LDAP), the weakness type (out-of-bounds write), that it can be triggered over a network by an unauthorized attacker, and the 9.8 score.
- Not stated in the research: affected Windows versions, fixed builds or KB numbers, the exact attack vector details, whether specific ports or LDAP over TLS are involved, and whether any exploitation has occurred.
- CISA KEV: the record shows no Known Exploited Vulnerabilities entry as of publication. That is not proof that nobody is exploiting it.
Understanding the weakness
An out-of-bounds write (CWE-787) happens when software writes data past the end, or before the start, of the memory it was meant to use. At best this crashes the service. At worst, an attacker who controls what gets written can corrupt adjacent memory and take over the process, which is how this class of bug becomes code execution.
The description says an unauthorized attacker can trigger it over a network. In practice that means the risk centers on systems that accept LDAP requests from other machines. On a Windows domain, those are typically domain controllers. A compromise of a directory server would be serious because directories hold account and authorization data for the rest of the environment.
Who is realistically exposed
- Domain controllers and other Windows servers that answer LDAP queries.
- Servers where LDAP is reachable from untrusted network segments, for example flat networks, VPN client ranges or partner links.
- Hosting and agency environments where a Windows directory supports web applications, intranets or single sign-on.
- Any system where LDAP ports are accidentally published to the internet.
Whether client-side Windows LDAP use is also affected is not stated in the research. Until Microsoft clarifies, assume servers are the highest priority and workstations come next.
How to check your exposure
Start with an inventory. Find which hosts answer LDAP and who can reach them. The standard LDAP ports are 389 (LDAP) and 636 (LDAP over TLS); the research does not say which ports this bug involves, so review both. The command below, run in PowerShell on a Windows server, lists listening TCP sockets on those ports. Any output means the host is acting as an LDAP server.
Get-NetTCPConnection -State Listen | Where-Object { $_.LocalPort -in 389,636 } | Select-Object LocalAddress,LocalPort,OwningProcessNext, record the installed Windows build so you can compare it with the fixed build once Microsoft publishes it. This read-only command prints the OS caption and build number.
Get-CimInstance Win32_OperatingSystem | Select-Object Caption,Version,BuildNumberFrom outside your network, verify that LDAP ports are not reachable from the internet. A Webforta Scan of a verified site can help you see what is publicly exposed, though internal directory servers need an internal review.
What to do now
- Open the Microsoft update guide entry for CVE-2026-119958 and read which Windows versions are affected and which update fixes it.
- List all domain controllers and LDAP-serving Windows hosts, and record their current build numbers.
- Test and deploy the Microsoft security update to domain controllers first, then other LDAP servers, following your normal change process.
- Block inbound LDAP (389) and LDAPS (636) from the internet and from any network segment that does not need them.
- Restrict LDAP access to known application servers and admin networks using host or network firewall rules.
- Turn on logging for domain controller crashes and unexpected service restarts so you can spot attempts.
- If you cannot patch quickly, record the compensating controls you applied and set a date to revisit.
Once the update is installed, rerun the build check above and confirm the number matches the fixed build named by Microsoft.
Detection and monitoring
No indicators of compromise are in the research, so there is nothing specific to hunt for yet. General signals worth watching on LDAP servers include unexpected crashes or restarts of the directory service, new inbound connections to ports 389 and 636 from unfamiliar addresses, and new administrator accounts or changed group memberships.
Memory corruption attempts often show up first as instability. Treat repeated service faults on a domain controller as a reason to investigate, not just restart. If you suspect compromise, follow a structured process such as Website hacked: what to do.
For public-facing parts of your estate, Webforta Monitor can alert you to certificate, DNS and header changes, which helps catch follow-on tampering, but it does not see inside an internal directory service.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
