dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-59196

HIGH · 7.0 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 10.0.10240.21161 / 10.0.14393.8519 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 during concurrent execution allows a locally authenticated attacker to elevate privileges to higher permission levels.

MitigationApply the Microsoft security update for this CVE when released. Until then, minimize local attack surface by restricting user permissions and monitoring for suspicious process activity targeting the SSDP service.

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 1507Operating system
Affected:< 10.0.10240.21161
Windows 10 1607Operating system
Affected:< 10.0.14393.8519
Windows 10 1809Operating system
Affected:< 10.0.17763.7919
Windows 10 21h2Operating system
Affected:< 10.0.19044.6456
Windows 10 22h2Operating system
Affected:< 10.0.19045.6456
Windows 11 22h2Operating system
Affected:< 10.0.22621.6060
Windows 11 23h2Operating system
Affected:<= 10.0.22631.6060
Windows 11 24h2Operating system
Affected:< 10.0.26100.6899

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. Identify if SSDP service is running
    Open Services (services.msc) or run 'Get-Service SSDPRedirector' in PowerShell to check if the SSDP service is active
    Affected if SSDP service is running on a vulnerable Windows version - the race condition only applies when the service is active
  2. Determine Windows version and build
    Run 'winver' or execute 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' in Command Prompt to obtain the exact Windows build number
    Affected if Build number falls below the fixed versions: <10.0.10240.21161 (1507), <10.0.14393.8519 (1607), <10.0.17763.7919 (1809), <10.0.19044.6456 (21h2), <10.0.19045.6456 (22h2), <10.0.22621.6060 (11 22h2), <=10.0.22631.6060 (11 23h2), <10.0.26100.6899 (11 24h2)
  3. Check current user privilege context
    Run 'whoami /groups' in Command Prompt or 'whoami /priv' to see current user permissions and group memberships
    Affected if User has limited or standard privileges - the vulnerability allows escalation from low-privilege authenticated access to higher permissions

Environment is affected if the SSDP service is running on a Windows version with a build number below the thresholds listed above, and the user is a local authenticated attacker with limited privileges who could exploit the race condition.

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.10240.21161 / 10.0.14393.8519 / 10.0.17763.7919 or later
Fixed in 10.0.10240.2116110.0.14393.851910.0.17763.7919
Interim mitigation

Apply the Microsoft security update for this CVE when released. Until then, minimize local attack surface by restricting user permissions and monitoring for suspicious process activity targeting the SSDP service.

Recommended fix High confidence

Install the Windows security update for CVE-2025-59196 (latest cumulative update for your Windows version)

  1. Open Windows Settings by pressing Win+I
  2. Navigate to Update & Security > Windows Update
  3. Click 'Check for updates' to download and install the latest security update
  4. If prompted to restart, restart the device to apply the update
  5. After updating, verify the build number matches or exceeds the fixed version for your Windows release
Caveat Standard Windows update - no expected breaking changes for this security patch

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59196 — 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-2025-59196 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