CVE-2022-26919
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedWindows Lightweight Directory Access Protocol (LDAP) Remote Code Execution Vulnerability
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis is a remote code execution vulnerability in Windows Lightweight Directory Access Protocol (LDAP). The vulnerability allows an attacker to execute arbitrary code on affected Windows systems via specially crafted LDAP requests, likely due to insufficient validation of LDAP protocol messages.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versions= 20h2= 21h1= 21h2= 1607= 1809= 1909all versionsall versionsall versionsall versionsall versions= r2all versions= r2all versions= 20h2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Windows versionRun 'winver' or 'systeminfo' or 'Get-ComputerInfo | Select-Object OsName,OsVersion' to identify the installed Windows version and build numberAffected if The version matches Windows 10 (1607, 1809, 1909, 20h2, 21h1, 21h2), Windows 11, Windows 7, Windows 8.1, Windows Rt 8.1, Windows Server 2008/2008 R2, Windows Server 2012/2012 R2, or Windows Server 2016 (including 20h2)
-
Verify Active Directory Domain Services role is installedRun 'Get-WindowsFeature -Name AD-Domain-Services' on Server systems, or check if the 'Active Directory Domain Services' Windows feature is present. On any system, check if the 'NTDS' process is running, which indicates a domain controllerAffected if The system is running as a domain controller or has the AD DS role installed (NTDS process is active)
-
Confirm LDAP service is listening on the networkRun 'Get-NetTCPConnection -LocalPort 389,636 -State Listen' or use 'netstat -an | findstr :389' to check if LDAP ports (389/tcp, 636/tcp) are bound and listeningAffected if LDAP ports 389/tcp or 636/tcp are in a listening state, exposing the service to network requests
A system is affected if it runs an affected Windows version AND runs Active Directory Domain Services (domain controller) with LDAP ports exposed to the network.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the relevant Windows security update (KBXXXXXX) to all affected Windows servers and workstations, prioritizing domain controllers and systems running the LDAP service.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,192.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-26919 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-26919 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data