CVE-2026-32082
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 · uneditedConcurrent execution using shared resource with improper synchronization ('race condition') in Windows SSDP Service allows an authorized attacker to elevate privileges 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 · moderate confidenceA race condition exists in the Windows SSDP (Simple Service Discovery Protocol) Service where improper synchronization of shared resources allows an authorized attacker to manipulate timing and elevate privileges locally to a higher integrity level.
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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/PR:L/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.
-
Confirm the SSDP service exists on the systemRun 'Get-Service -Name SSDPSRV' or 'sc query SSDPSRV' in PowerShell/Command Prompt to check if the Simple Service Discovery Protocol service is present.Affected if The service is present and enumerated in the service control manager.
-
Retrieve the current Windows build versionRun 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to display the installed Windows version and build number.Affected if The build version falls below any of the following 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).
-
Check if the SSDP service is runningRun 'Get-Service -Name SSDPSRV | Select-Object Status' or 'sc queryex SSDPSRV' to determine the current running state of the service.Affected if The service is in a running state, as the race condition vulnerability requires the SSDP service to be active for exploitation.
-
Query the exact CurrentBuild and DisplayBuild in the registryRun 'reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentBuild' and 'reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v DisplayBuild' to obtain precise build numbers for comparison.Affected if The combined build number (CurrentBuild.DisplayBuild) is lower than the affected version thresholds listed in the CVE.
A system is affected if it runs a Windows version with a build number lower than the thresholds AND has the SSDP service available and running, as the race condition only triggers when the service is active.
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 this vulnerability when released. If the SSDP service is not required, consider disabling it to reduce attack surface.
Apply the Microsoft security update for CVE-2026-32082, which raises the build to 10.0.14393.9060 (Win10 1607), 10.0.17763.8644 (Win10 1809), 10.0.19044.7184 (Win10 21h2), 10.0.19045.7184 (Win10 22h2), 10.0.22631.6936 (Win11 23h2), 10.0.26100.8246 (Win11 24h2), 10.0.26200.8246 (Win11 25h2), or 10.0.
- Identify the current Windows version and build by running 'winver' or 'systeminfo' in Command Prompt
- Open Windows Settings and navigate to Windows Update, or run 'ms-settings:windowsupdate'
- Check for and install the latest Windows security updates that address this vulnerability
- After updating, verify the build number matches or exceeds the fixed version for your Windows release: 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
- Confirm the SSDP Service (UxSms) is properly updated by checking the file version of %SystemRoot%\System32\ssdpsrv.dll after reboot
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32082 — 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-32082 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