dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-59209

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 · moderate confidence

This is a local information disclosure vulnerability in Windows Push Notification Core. An authorized attacker with local access can exploit this to disclose sensitive information. The vulnerability stems from improper access controls within the notification system component.

MitigationApply the latest Microsoft security updates for Windows to patch the Push Notification Core component. Verify that push notification functionality continues to work correctly after patching.

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 build version
    Run 'winver' from command prompt or check System Properties to see the OS Build number (for example, 19045.6456)
    Affected if The build number falls below the threshold for your Windows release (e.g., Windows 10 22h2 < 10.0.19045.6456, Windows 11 23h2 <= 10.0.22631.6060)
  2. Verify exact version via registry
    Run 'reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentBuild' and '/v DisplayVersion' to get precise build values
    Affected if The CurrentBuild value is lower than the version-specific threshold for your installed Windows release
  3. Confirm Windows release name
    Run 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to identify your specific Windows 10 or 11 release (such as 1507, 1607, 1809, 21h2, 22h2, or Windows 11 22h2/23h2/24h2)
    Affected if The identified release combined with its build number matches an affected version range listed in the CVE
  4. Verify Push Notification component presence
    Check that the Windows Push Notification service (PushToInstall or related WPN services) is available on the system by running 'Get-Service -Name Push*' in PowerShell
    Affected if The system has Push Notification capabilities and the OS version/build falls within the affected ranges

You are affected if your Windows version and build number match any of the affected ranges listed, and the Push Notification component is present on your system.

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 latest Microsoft security updates for Windows to patch the Push Notification Core component. Verify that push notification functionality continues to work correctly after patching.

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.7500 or later | Windows 11 24h2: 10.0.26100.6899 or later

  1. Open Settings on the Windows device
  2. Navigate to Windows Update (Settings > Windows Update)
  3. Click 'Check for updates' to download and install the latest security updates
  4. Ensure the system restarts if prompted to complete the installation
  5. Alternatively, manually download the security update from the Microsoft Update Catalog (catalog.update.microsoft.com) for your specific Windows version
  6. After installation, verify the installed build number matches or exceeds the fixed version for your Windows release
Caveat Standard Windows security update - no breaking changes expected for typical deployments

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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