CVE-2025-53724
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 · uneditedAccess 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 confidenceA type confusion vulnerability in Windows Push Notifications allows an authenticated local attacker to elevate privileges by exploiting how the notification system handles resource access with incompatible types.
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< 10.0.10240.21100< 10.0.14393.8330< 10.0.17763.7678< 10.0.19044.6216< 10.0.19045.6216< 10.0.22621.5768< 10.0.22631.5768< 10.0.26100.4851CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Windows version and build numberOpen Command Prompt and run `winver` or run `systeminfo` in PowerShell and look for the OS Name and OS Version lines. Alternatively, run `Get-ComputerInfo | Select-Object OsName, OsVersion, OsBuildNumber` in PowerShell.Affected if The build number is lower than any of these thresholds: 10240.21100 (Win10 1507), 14393.8330 (Win10 1607), 17763.7678 (Win10 1809), 19044.6216 (Win10 21h2), 19045.6216 (Win10 22h2), 22621.5768 (Win11 22h2), 22631.5768 (Win11 23h2), or 26100.4851 (Win11 24h2).
-
Verify Windows Push Notifications service statusOpen Services (services.msc) and locate 'Windows Push Notifications' service, or run `Get-Service | Where-Object {$_.Name -like '*Push*'}` in PowerShell.Affected if The Windows Push Notifications service exists and is running on an unpatched Windows version.
-
Check for installed security updates for CVE-2025-53724Run `Get-HotFix | Where-Object {$_.Description -like '*Security*'}` in PowerShell to list security updates, or view the Windows Update History in Settings > Windows Update > Update History. Look for updates installed after the patch date.Affected if No security update addressing CVE-2025-53724 appears in the installed updates list on an affected Windows version.
-
Confirm user has local authenticated accessThis vulnerability requires an authenticated local user account. Verify that untrusted or low-privilege local accounts exist on the system by running `Get-LocalUser` in PowerShell.Affected if The system has local user accounts (non-domain) and runs an unpatched Windows version with Push Notifications enabled.
A system is affected if it runs any Windows 10 or 11 version with a build number below the thresholds listed and has the Windows Push Notifications feature active without the CVE-2025-53724 security update installed.
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.0.10240.2110010.0.14393.833010.0.17763.7678
Apply Microsoft security updates for CVE-2025-53724 to Windows systems; prioritize endpoints where local unprivileged access exists.
Install the latest Windows cumulative security update containing the CVE-2025-53724 fix. Specific builds: 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: 1
- Open Windows Settings and navigate to Update & Security > Windows Update
- Click 'Check for updates' to download and install the latest cumulative security update for your Windows version
- Alternatively, manually install the appropriate KB update from Microsoft's Catalog for your specific Windows build: KB50XXXX (check MSRC for the exact KB number for CVE-2025-53724)
- Restart the system after installing the update
- Verify the installed build version matches or exceeds the fixed version for your Windows release (e.g., Windows 10 22h2 should be >= 10.0.19045.6216)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-53724 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-53724 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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