dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-32083

HIGH · 7.0 CVSS v3.1 Published 2026-04-14
Fix available
A fix is available. Upgrade to 10.0.14393.9060 / 10.0.17763.8644 or later.
See remediation →
72/100
Remediation priority · Elevated
Zero-click

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 · unedited
Concurrent 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 confidence

A race condition vulnerability exists in the Windows SSDP (Simple Service Discovery Protocol) Service where improper synchronization of shared resources allows a locally authorized attacker to exploit the timing window and elevate privileges to higher permission levels.

MitigationApply the Microsoft security update for this vulnerability through standard Windows patch management processes. Verify the SSDP Service functions normally after patching.

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
Windows 10 1607Operating system
Affected:< 10.0.14393.9060
Windows 10 1809Operating system
Affected:< 10.0.17763.8644
Windows 10 21h2Operating system
Affected:< 10.0.19044.7184
Windows 10 22h2Operating system
Affected:< 10.0.19045.7184
Windows 11 23h2Operating system
Affected:< 10.0.22631.6936
Windows 11 24h2Operating system
Affected:< 10.0.26100.8246
Windows 11 25h2Operating system
Affected:< 10.0.26200.8246
Windows 11 26h1Operating system
Affected:< 10.0.28000.1836

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Windows version and build number
    Open Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to display the installed Windows version and build number.
    Affected if The displayed build number falls below any of these thresholds: 14393.9060, 17763.8644, 19044.7184, 19045.7184, 22631.6936, 26100.8246, 26200.8246, or 28000.1836 depending on your Windows release.
  2. Identify Windows release version
    Run 'winver' to confirm whether you are on Windows 10 1607, 1809, 21h2, 22h2, or Windows 11 23h2, 24h2, 25h2, or 26h1.
    Affected if Your Windows release corresponds to one of the affected versions listed and the build number is below the corresponding threshold.
  3. Verify SSDP Service status
    Open Services (services.msc) or run 'Get-Service SSDP' in PowerShell to check if the SSDP Discovery Service is installed and its current state (Running/Stopped).
    Affected if The SSDP Service is present on the system and is running; however, note that the vulnerability could still apply even if the service is disabled since the race condition exists in the service code itself.
  4. Confirm service executable exists
    Check if the SSDP service binary exists at the expected path by running 'Get-WmiObject win32_service | Where-Object {$_.Name -eq "SSDP"}' in PowerShell to retrieve service details including the executable path.
    Affected if The SSDP service is registered on the system.

You are affected if your Windows version and build number match any of the affected release/build combinations AND the SSDP Service is present on your system.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 10.0.14393.9060 / 10.0.17763.8644 / 10.0.19044.7184 or later
Fixed in 10.0.14393.906010.0.17763.864410.0.19044.7184
Interim mitigation

Apply the Microsoft security update for this vulnerability through standard Windows patch management processes. Verify the SSDP Service functions normally after patching.

Recommended fix High confidence

Upgrade to the latest Windows 10 or Windows 11 build that includes the CVE-2026-32083 security patch (minimum build numbers listed in steps)

  1. Open Settings > Update & Security > Windows Update
  2. Click 'Check for updates' to download and install the latest security updates
  3. Ensure the update includes the build number >= to the fixed version for your Windows edition: 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
  4. Verify the installed version by running 'winver' command to confirm the build number matches or exceeds the fixed version
Caveat Standard Windows update risks - ensure backups of critical data before applying updates

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32083 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-32083 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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