dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-42970

MEDIUM · 5.5 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 10.0.14393.9234 / 10.0.17763.8880 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 Notifications 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 Notifications. An authorized attacker can exploit this to disclose sensitive information to an unauthorized actor locally. The vulnerability affects the Windows Push Notifications component and requires local access with low privileges to exploit.

MitigationApply the relevant Microsoft security update for Windows Push Notifications once released. As this is a local vulnerability, ensure systems are patched through standard Windows Update processes and verify the patch deployment.

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 1607Operating system
Affected:< 10.0.14393.9234
Windows 10 1809Operating system
Affected:< 10.0.17763.8880
Windows 10 21h2Operating system
Affected:< 10.0.19044.7417
Windows 10 22h2Operating system
Affected:< 10.0.19045.7417
Windows 11 23h2Operating system
Affected:< 10.0.22631.7219
Windows 11 24h2Operating system
Affected:< 10.0.26100.8655
Windows 11 25h2Operating system
Affected:< 10.0.26200.8655
Windows 11 26h1Operating system
Affected:< 10.0.28000.2269

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 installed Windows version
    Open Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to obtain the exact build number
    Affected if The installed build number falls below any of these thresholds: 14393.9234 (Win10 1607), 17763.8880 (Win10 1809), 19044.7417 (Win10 21h2), 19045.7417 (Win10 22h2), 22631.7219 (Win11 23h2), 26100.8655 (Win11 24h2), 26200.8655 (Win11 25h2), or 28000.2269 (Win11 26h1)
  2. Verify Push Notifications service status
    Open Services console (services.msc) or run 'Get-Service WpnUserService' in PowerShell to check if the Windows Push Notifications User Service is present and running
    Affected if The WpnUserService is installed and running on the system
  3. Check notification subsystem components
    Inspect the presence of notification-related DLLs in %SystemRoot%\System32\ folder, specifically looking for wpncore.dll or related push notification components, using 'dir %SystemRoot%\System32\wpn*' in Command Prompt
    Affected if Windows Push Notification subsystem files exist on the system

You are affected if your Windows version is below the patched build numbers listed AND the Windows Push Notifications feature is enabled or the WpnUserService 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.14393.9234 / 10.0.17763.8880 / 10.0.19044.7417 or later
Fixed in 10.0.14393.923410.0.17763.888010.0.19044.7417
Interim mitigation

Apply the relevant Microsoft security update for Windows Push Notifications once released. As this is a local vulnerability, ensure systems are patched through standard Windows Update processes and verify the patch deployment.

Recommended fix High confidence

Windows 10 1607: build 10.0.14393.9234 | Windows 10 1809: build 10.0.17763.8880 | Windows 10 21h2: build 10.0.19044.7417 | Windows 10 22h2: build 10.0.19045.7417 | Windows 11 23h2: build 10.0.22631.7219 | Windows 11 24h2: build 10.0.26100.8655 | Windows 11 25h2: build 10.0.26200.8655 | Windows 11 26

  1. Open Windows Settings by pressing Win + I
  2. Navigate to 'Update & Security' and click 'Windows Update'
  3. Click 'Check for updates' to download and install the latest cumulative security update
  4. Restart the computer if prompted to complete the installation
  5. Verify the installed build number matches or exceeds the fixed version for your Windows edition (e.g., for Windows 10 22h2, verify build 10.0.19045.7417 or higher)
Caveat Standard Windows update - no breaking changes expected for this security patch

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

Fix this in Windows 10 1607 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-2026-42970 — 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-2026-42970 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