dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-47975

HIGH · 7.0 CVSS v3.1 Published 2025-07-08
Fix available
A fix is available. Upgrade to 10.0.10240.21073 / 10.0.14393.8246 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
Double free 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 double-free memory corruption vulnerability in the Windows SSDP (Simple Service Discovery Protocol) service allows a locally authenticated attacker to corrupt memory references and potentially execute arbitrary code with elevated privileges.

MitigationApply the relevant Microsoft security update for CVE-2025-47975 through Windows Update or manual patch deployment to address the double-free vulnerability in 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.21073
Windows 10 1607Operating system
Affected:< 10.0.14393.8246
Windows 10 1809Operating system
Affected:< 10.0.17763.7558
Windows 10 21h2Operating system
Affected:< 10.0.19044.6093
Windows 10 22h2Operating system
Affected:< 10.0.19045.6093
Windows 11 22h2Operating system
Affected:< 10.0.22621.5624
Windows 11 23h2Operating system
Affected:< 10.0.22631.5624
Windows 11 24h2Operating system
Affected:< 10.0.26100.4652

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. Determine Windows version and build number
    Open Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to obtain the full version and build number.
    Affected if The build number falls below any of these thresholds: 10240.21073 (1507), 14393.8246 (1607), 17763.7558 (1809), 19044.6093 (21h2), 19045.6093 (22h2), 22621.5624 (11 22h2), 22631.5624 (11 23h2), 26100.4652 (11 24h2)
  2. Verify SSDP service status
    Open Services console (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 Discovery service is present and currently running on the system.
  3. Confirm service is set to start
    Run 'Get-Service SSDP* | Select-Object Name,StartType,Status' in PowerShell or check the service properties in services.msc to see the startup type configuration.
    Affected if The SSDP Discovery service is set to Automatic or Manual startup, meaning it could be running or could be started.
  4. Check for CVE-2025-47975 security update
    Open Settings > Windows Update > View update history, or run 'Get-HotFix | Where-Object {$_.Description -like "Security Update"} | Sort-Object InstalledOn -Descending | Select-Object -First 10' to list recent security patches.
    Affected if The specific security update addressing CVE-2025-47975 is not listed among installed updates.

A system is affected if it runs a Windows version with a build number below the thresholds listed AND has the SSDP Discovery service enabled or running.

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.21073 / 10.0.14393.8246 / 10.0.17763.7558 or later
Fixed in 10.0.10240.2107310.0.14393.824610.0.17763.7558
Interim mitigation

Apply the relevant Microsoft security update for CVE-2025-47975 through Windows Update or manual patch deployment to address the double-free vulnerability in the SSDP Service.

Recommended fix High confidence

Windows 10 1507: 10.0.10240.21073+ | Windows 10 1607: 10.0.14393.8246+ | Windows 10 1809: 10.0.17763.7558+ | Windows 10 21h2: 10.0.19044.6093+ | Windows 10 22h2: 10.0.19045.6093+ | Windows 11 22h2: 10.0.22621.5624+ | Windows 11 23h2: 10.0.22631.5624+ | Windows 11 24h2: 10.0.26100.4652+

  1. Open Settings > Update & Security > Windows Update and check for updates
  2. Install all available security updates for your Windows version
  3. If using WSUS, approve the relevant security update for your systems
  4. For enterprise deployments, use SCCM/Intune to deploy the cumulative security update
  5. Restart the system after applying updates
  6. Verify the SSDP Service (Social Security Disaster Prevention) is running normally post-update
Caveat Standard Windows security update risks - verify compatibility with line-of-business applications before broad deployment

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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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