CVE-2026-32072
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 · uneditedImproper authentication in Windows Active Directory allows an unauthorized attacker to perform spoofing locally.
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 · low confidenceImproper authentication vulnerability in Windows Active Directory enables an unauthorized local attacker to perform spoofing attacks by bypassing or manipulating authentication mechanisms.
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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 build versionRun 'winver' or 'systeminfo | findstr /C:"OS Version"' to obtain the installed Windows build numberAffected if The build number is lower than the threshold for your Windows version (1607: <14393.9060, 1809: <17763.8644, 21h2: <19044.7184, 22h2: <19045.7184, 23h2: <22631.6936, 24h2: <26100.8246, 25h2: <26200.8246, 26h1: <28000.1836)
-
Confirm Active Directory roleRun 'netdom /query /domain:%USERDOMAIN%' or check System Properties to see if the machine is joined to an Active Directory domainAffected if The system is joined to an Active Directory domain and the Windows version is below the fixed build thresholds
-
Identify domain controller statusRun 'nltest /dsgetdc:domainname' or check 'Get-ADDomain' PowerShell cmdlet if Domain Controller role is presentAffected if The affected system is a Domain Controller or a member server handling AD authentication on a vulnerable Windows version
You are affected if your Windows version/build is below the specified threshold AND the system uses Active Directory for authentication.
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 Microsoft security updates for Windows Active Directory and review AD authentication protocols and trust relationships.
Upgrade to 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), or Windows 11 26h1 (>=10.0.280
- Open Settings > System > Windows Update and check for updates
- Alternatively, verify current Windows version by running 'winver' in the Run dialog
- Download and install the appropriate Windows security update from Microsoft Update Catalog that corresponds to your version (KB references can be found on MSRC for this CVE)
- Restart the system after update installation
- Verify the installed version matches or exceeds the fixed version for your Windows release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32072 — 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-32072 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