dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-48815

HIGH · 7.8 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 →
80/100
Remediation priority · High
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
Access of resource using incompatible type ('type confusion') 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 type confusion vulnerability in the Windows SSDP (Simple Service Discovery Protocol) Service allows a locally authorized attacker to manipulate object type handling within the service, leading to memory corruption and privilege escalation from authenticated user to higher system privileges.

MitigationApply Microsoft security updates for Windows when released; in the interim, restrict user access to the SSDP service, disable the service if not required, and follow least-privilege principles to limit local attack surface.

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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/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 build number
    Run 'winver' or 'systeminfo' and note the OS Build number (for example, 19045.5047)
    Affected if The build number falls below the threshold for your Windows release: 10.0.10240.21073 (1507), 10.0.14393.8246 (1607), 10.0.17763.7558 (1809), 10.0.19044.6093 (21h2), 10.0.19045.6093 (22h2), 10.0.22621.5624 (11 22h2), 10.0.22631.5624 (11 23h2), or 10.0.26100.4652 (11 24h2)
  2. Verify SSDP service is installed
    Run 'Get-Service SSDPService' in PowerShell or 'sc query SSDPService' in Command Prompt
    Affected if The service SSDPService exists on the system (service name may display as 'SSDP')
  3. Check if SSDP service is running
    Run 'Get-Service SSDPService' and verify the Status value, or run 'sc query SSDPService' and check the STATE line
    Affected if The SSDP service is in a running state (STATE: RUNNING)

Your environment is affected only if you are running a Windows version with a build number below the threshold for your specific release AND the SSDP service is installed and running 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.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 Microsoft security updates for Windows when released; in the interim, restrict user access to the SSDP service, disable the service if not required, and follow least-privilege principles to limit local attack surface.

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 Windows security updates, which will include the fix for CVE-2025-48815
  3. Restart the system if prompted to complete the installation
  4. Verify the update was installed by checking Windows Update history or running 'winver' to confirm the build number meets or exceeds the minimum fixed version for your Windows release
Caveat Standard Windows security update; no expected breaking changes but enterprise deployments should test in staging environment

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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