dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-59211

MEDIUM · 5.5 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 10.0.10240.21161 / 10.0.14393.8519 or later.
See remediation →
57/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
Exposure of sensitive information to an unauthorized actor in Windows Push Notification Core allows an authorized attacker to disclose information 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 · high confidence

CVE-2025-59211 is a local information disclosure vulnerability in Windows Push Notification Core. An authorized (but local) attacker can exploit this to gain access to sensitive information that should be protected. The vulnerability has a CVSS of 5.5 (Medium), indicating limited but real impact to confidentiality.

MitigationApply the relevant Windows security update (KB) for this vulnerability through standard Windows Update or enterprise patch management systems. After patching, verify that Windows Push Notification functionality continues to operate correctly.

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.21161
Windows 10 1607Operating system
Affected:< 10.0.14393.8519
Windows 10 1809Operating system
Affected:< 10.0.17763.7919
Windows 10 21h2Operating system
Affected:< 10.0.19044.6456
Windows 10 22h2Operating system
Affected:< 10.0.19045.6456
Windows 11 22h2Operating system
Affected:< 10.0.22621.6060
Windows 11 23h2Operating system
Affected:<= 10.0.22631.6060
Windows 11 24h2Operating system
Affected:< 10.0.26100.6899

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
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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 major version and build number
    Run `systeminfo` from command prompt and look at OS Name and OS Version lines, or run `winver` and note the version and build number displayed
    Affected if The displayed build number falls below the affected thresholds: 10240.21161 for 1507, 14393.8519 for 1607, 17763.7919 for 1809, 19044.6456 for 21h2, 19045.6456 for 22h2, 22621.6060 for 11 22h2, 22631.6060 for 11 23h2, or 26100.6899 for 11 24h2
  2. Confirm Windows release name matches version
    Run `winver` and match the release (such as 'Version 22H2' or 'Windows 11 23H2') to the corresponding build number from step 1
    Affected if The release name does not match a supported, patched branch or the associated build is below the threshold for that release branch
  3. Verify Push Notification component is present
    Check that the Windows Push Notification service exists by querying the registry at HKLM\SYSTEM\CurrentControlSet\Services\WpnService or checking for WpnService.exe in the system
    Affected if The service exists (which is the default state for most Windows installations), indicating the vulnerable component is present

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.21161 / 10.0.14393.8519 / 10.0.17763.7919 or later
Fixed in 10.0.10240.2116110.0.14393.851910.0.17763.7919
Interim mitigation

Apply the relevant Windows security update (KB) for this vulnerability through standard Windows Update or enterprise patch management systems. After patching, verify that Windows Push Notification functionality continues to operate correctly.

Recommended fix High confidence

Windows 10 1507: 10.0.10240.21161 | Windows 10 1607: 10.0.14393.8519 | Windows 10 1809: 10.0.17763.7919 | Windows 10 21h2: 10.0.19044.6456 | Windows 10 22h2: 10.0.19045.6456 | Windows 11 22h2: 10.0.22621.6060 | Windows 11 23h2: 10.0.22631.6060 or later | Windows 11 24h2: 10.0.26100.6899 or later

  1. Open Windows Settings and navigate to Update & Security > Windows Update
  2. Click 'Check for updates' to download and install the security update for CVE-2025-59211
  3. Restart the system if prompted to complete the installation
  4. Verify the update was installed by checking Windows Update history - the update should appear as a security update installed on the system date
Caveat Standard Windows security update - no breaking changes expected for this information disclosure vulnerability patch

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
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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