CVE-2026-32071
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 · uneditedNull pointer dereference in Windows Local Security Authority Subsystem Service (LSASS) allows an unauthorized attacker to deny service over a network.
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 confidenceA null pointer dereference vulnerability in the Windows Local Security Authority Subsystem Service (LSASS) allows unauthenticated remote attackers to crash the LSASS process, causing a denial of service on affected Windows systems.
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 data< 10.0.14393.9060< 10.0.17763.8644< 10.0.19044.7184< 10.0.19045.7184< 10.0.22631.6936< 10.0.26100.8246< 10.0.26200.8246< 10.0.28000.1836CVSS 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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.
-
Identify Windows versionRun 'winver' from command prompt or execute 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to retrieve the installed Windows version and build numberAffected if The displayed build number is lower than any of these thresholds: 14393.9060 (Win10 1607), 17763.8644 (Win10 1809), 19044.7184 (Win10 21h2/22h2), 22631.6936 (Win11 23h2), 26100.8246 (Win11 24h2/25h2), or 28000.1836 (Win11 26h1)
-
Confirm LSASS process is runningOpen Task Manager, go to Details tab, and locate 'lsass.exe' in the list, or run 'tasklist /FI "IMAGENAME eq lsass.exe"' from an elevated command promptAffected if The lsass.exe process is present and running (this is the default state on Windows systems, especially domain-joined machines)
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.
dbcve · scoped10.0.14393.906010.0.17763.864410.0.19044.7184
Apply the relevant Microsoft security update for this LSASS vulnerability; prior to deployment, validate backup and recovery procedures in case patch application causes issues with domain authentication.
Apply the appropriate Windows Security Update (CVE-2026-32071) for your Windows version to reach the fixed build number
- Open Windows Settings and navigate to Update & Security > Windows Update
- Click 'Check for updates' to download and install the latest security updates
- Alternatively, manually download the security update from the Microsoft Update Catalog (catalog.update.microsoft.com) for your specific Windows version
- Restart the system after installing the updates to ensure LSASS is updated
- Verify the installed version matches or exceeds the fixed build: Windows 10 1607: 10.0.14393.9060, Windows 10 1809: 10.0.17763.8644, Windows 10 21h2: 10.0.19044.7184, Windows 10 22h2: 10.0.19045.7184, Windows 11 23h2: 10.0.22631.6936, Windows 11 24h2: 10.0.26100.8246, Windows 11 25h2: 10.0.26200.8246, Windows 11 26h1: 10.0.28000.1836
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32071 — 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-2026-32071 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