dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-50155

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 where the system accesses a resource using an incompatible type, allowing a locally authorized attacker to elevate privileges to higher integrity levels.

MitigationApply the Microsoft security update for CVE-2025-50155 via Windows Update or enterprise patch management systems; prioritize endpoints with direct user access.

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. Check Windows build version
    Open Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to retrieve the full Windows build number
    Affected if The displayed build number falls below any of the following thresholds: 10.0.10240.21100 (Windows 10 1507), 10.0.14393.8330 (Windows 10 1607), 10.0.17763.7678 (Windows 10 1809), 10.0.19044.6216 (Windows 10 21h2), 10.0.19045.6216 (Windows 10 22h2), 10.0.22621.5768 (Windows 11 22h2), 10.0.22631.5768 (
  2. Query exact build via registry
    Run 'reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentBuild' and 'reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v DisplayVersion' to get the precise build number
    Affected if The CurrentBuild value is lower than the corresponding threshold for your Windows release branch as listed in step 1
  3. Confirm Windows 10 release branch
    Run 'reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v ReleaseId' to identify the specific Windows 10 release (1507, 1607, 1809, 21h2, or 22h2)
    Affected if The ReleaseId matches an affected version and the build number from steps 1-2 is below the corresponding threshold for that release

The system is affected if the installed Windows build number is lower than the threshold for its specific release branch, since the vulnerability exists in the Windows Push Notifications component of those unpatched versions.

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-50155 via Windows Update or enterprise patch management systems; prioritize endpoints with direct user access.

Recommended fix High confidence

Windows security update (KB) addressing CVE-2025-50155, which upgrades to: Windows 10 1507 to 10.0.10240.21100+, Windows 10 1607 to 10.0.14393.8330+, Windows 10 1809 to 10.0.17763.7678+, Windows 10 21h2 to 10.0.19044.6216+, Windows 10 22h2 to 10.0.19045.6216+, Windows 11 22h2 to 10.0.22621.5768+, Wi

  1. Identify current Windows version by running 'winver' or checking System Properties
  2. Determine the applicable security update for your Windows version from Microsoft's security update guide
  3. Apply the latest Windows security update (KB) for your Windows version, which will upgrade the build to at least the fixed version threshold
  4. Alternatively, enable automatic Windows Updates to receive the security patch automatically
  5. After update installation, restart the system to complete the remediation
  6. Verify the installed build version meets or exceeds the fixed version threshold for your Windows release
Caveat Standard Windows update risks; ensure critical data is backed up 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
  • 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-50155 — 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-50155 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