dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-53725

HIGH · 7.8 CVSS v3.1 Published 2025-08-12
Fix available
A fix is available. Upgrade to 10.0.10240.21100 / 10.0.14393.8330 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 Push Notifications 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

This is a type confusion vulnerability in the Windows Push Notifications component. The flaw allows a locally authenticated attacker to exploit improper type validation when accessing resources, enabling elevation of privileges from their current user context to a higher privilege level (likely SYSTEM).

MitigationApply the Microsoft security update for CVE-2025-53725 via Windows Update or patch management deployment to all affected Windows systems.

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.21100
Windows 10 1607Operating system
Affected:< 10.0.14393.8330
Windows 10 1809Operating system
Affected:< 10.0.17763.7678
Windows 10 21h2Operating system
Affected:< 10.0.19044.6216
Windows 10 22h2Operating system
Affected:< 10.0.19045.6216
Windows 11 22h2Operating system
Affected:< 10.0.22621.5768
Windows 11 23h2Operating system
Affected:< 10.0.22631.5768
Windows 11 24h2Operating system
Affected:< 10.0.26100.4851

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. Determine the installed Windows version
    Run 'winver' from the command prompt, or use 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"', or run 'Get-ComputerInfo | Select-Object WindowsProductName, WindowsVersion' in PowerShell
    Affected if The reported version falls below any of these thresholds: Windows 10 1507 < 10.0.10240.21100, Windows 10 1607 < 10.0.14393.8330, Windows 10 1809 < 10.0.17763.7678, Windows 10 21h2 < 10.0.19044.6216, Windows 10 22h2 < 10.0.19045.6216, Windows 11 22h2 < 10.0.22621.5768, Windows 11 23h2 < 10.0.22631.57
  2. Verify the Windows Push Notifications component is present
    Check that the WpnService (Windows Push Notification Service) is available on the system by running 'Get-Service -Name WpnService' in PowerShell or checking the service list via 'sc query WpnService'
    Affected if The system has the Windows Push Notifications component (WpnService) present and accessible to locally authenticated users
  3. Confirm local user access context
    Verify that untrusted local user accounts exist on the system by running 'Get-LocalUser' in PowerShell or checking via 'net user'
    Affected if The system allows local user authentication for non-privileged accounts, which is the typical default configuration for Windows workstations and servers

The environment is affected if the installed Windows version is lower than any of the version thresholds listed and the system has the Windows Push Notifications component accessible to locally authenticated users.

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.21100 / 10.0.14393.8330 / 10.0.17763.7678 or later
Fixed in 10.0.10240.2110010.0.14393.833010.0.17763.7678
Interim mitigation

Apply the Microsoft security update for CVE-2025-53725 via Windows Update or patch management deployment to all affected Windows systems.

Recommended fix High confidence

Windows 10 1507: 10.0.10240.21100 | Windows 10 1607: 10.0.14393.8330 | Windows 10 1809: 10.0.17763.7678 | Windows 10 21h2: 10.0.19044.6216 | Windows 10 22h2: 10.0.19045.6216 | Windows 11 22h2: 10.0.22621.5768 | Windows 11 23h2: 10.0.22631.5768 | Windows 11 24h2: 10.0.26100.4851

  1. Identify the current Windows version by running 'winver' in the Run dialog or checking Settings > System > About
  2. Determine which version branch your current installation belongs to (e.g., Windows 10 22h2, Windows 11 23h2)
  3. For Windows 10: Navigate to Settings > Update & Security > Windows Update and check for updates
  4. For Windows 11: Navigate to Settings > Windows Update and check for updates
  5. Install all pending security updates, specifically the patch for CVE-2025-53725
  6. Restart the system when prompted to complete the installation
  7. Verify the installed version matches or exceeds the fixed version for your branch using 'winver'
Caveat Standard Windows update applies; ensure backups of critical data before any system update as a precaution

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
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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