dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-48819

HIGH · 7.1 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 →
73/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
Sensitive data storage in improperly locked memory in Windows Universal Plug and Play (UPnP) Device Host allows an authorized attacker to elevate privileges over an adjacent network.

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

This vulnerability in Windows Universal Plug and Play (UPnP) Device Host stores sensitive data in improperly locked memory, allowing an authorized attacker on an adjacent network to access this data and elevate privileges.

MitigationApply the Microsoft security update for CVE-2025-48819 when released, and minimize attack surface by restricting adjacent network access to systems with UPnP Device Host enabled.

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

CVSS:3.1/AV:A/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. Verify UPnP Device Host is enabled
    Run PowerShell: Get-Service -Name upnphost | Select-Object Name,Status,StartType. Also check via Get-WindowsOptionalFeature -Online -FeatureName *UPnP*
    Affected if The UPnP Device Host service is running or the UPnP feature is enabled on the system
  2. Identify Windows version and build number
    Run winver or execute: systeminfo | findstr /B /C:"OS Name" /C:"OS Version". In PowerShell: [System.Environment]::OSVersion.Version.ToString() or (Get-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion').CurrentBuildNumber
    Affected if The detected build number falls below the 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)
  3. Confirm service executable version
    Locate the upnphost service binary. Default path is C:\Windows\System32\upnphost.dll or check the service via PowerShell: Get-Process | Where-Object {$_.ProcessName -like "*upnp*"}, then right-click Properties to see file version
    Affected if The file version of the UPnP Device Host component is lower than the security update version for CVE-2025-48819

A system is affected if UPnP Device Host is enabled and the Windows build number is below the version thresholds listed for the respective Windows release.

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 Microsoft security update for CVE-2025-48819 when released, and minimize attack surface by restricting adjacent network access to systems with UPnP Device Host enabled.

Recommended fix High confidence

Install the May 2025 Windows security update (KB[insert relevant KB number from MSRC]) to achieve the fixed build version for your Windows release (e.g., Windows 10 22h2: build 10.0.19045.6093 or higher, Windows 11 23h2: build 10.0.22631.5624 or higher)

  1. Identify the current Windows build version by running 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"'
  2. Open Windows Update by pressing Windows key and typing 'Check for updates' or navigate to Settings > Update & Security > Windows Update
  3. Click 'Check for updates' to download and install the latest security updates for your Windows version
  4. Alternatively, manually download the specific security update from the Microsoft Update Catalog (search for the KB article associated with this CVE - May 2025 security updates)
  5. After installation, restart the computer when prompted
  6. Verify the fix is applied by checking the installed updates: go to Settings > Apps > Apps & features > Microsoft Windows > Advanced options, or run 'winver' to confirm the build number matches or exceeds the fixed version for your Windows release
Caveat No breaking changes expected; this is a routine security patch. As a precaution, back up critical data before applying updates.

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
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,820
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,912.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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