dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-24282

MEDIUM · 5.5 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to 10.0.14393.8957 / 10.0.17763.8511 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
Out-of-bounds read in Push Message Routing Service 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

An out-of-bounds read vulnerability exists in the Push Message Routing Service where improper bounds validation during memory access allows an authenticated local attacker to read adjacent memory contents, potentially exposing sensitive information.

MitigationApply vendor-provided security patches for the Push Message Routing Service and implement proper bounds checking in memory access operations.

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.8957
Windows 10 1809Operating system
Affected:< 10.0.17763.8511
Windows 10 21h2Operating system
Affected:< 10.0.19044.7058
Windows 10 22h2Operating system
Affected:< 10.0.19045.7058
Windows 11 23h2Operating system
Affected:< 10.0.22631.6783
Windows 11 24h2Operating system
Affected:< 10.0.26100.7979
Windows 11 25h2Operating system
Affected:< 10.0.26200.7979
Windows 11 26h1Operating system
Affected:< 10.0.28000.1719

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 version number
    Run 'winver' from the Run dialog or execute 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' in Command Prompt
    Affected if The displayed version falls within any of the following ranges: 10.0.14393.x before 8957, 10.0.17763.x before 8511, 10.0.19044.x before 7058, 10.0.19045.x before 7058, 10.0.22631.x before 6783, 10.0.26100.x before 7979, 10.0.26200.x before 7979, or 10.0.28000.x before 1719
  2. Confirm exact OS build number
    Run 'winver' or go to Settings > System > About to view the exact Build number displayed
    Affected if The build number is lower than the threshold for your specific Windows release (1607, 1809, 21h2, 22h2, 23h2, 24h2, 25h2, or 26h1)
  3. Identify the Push Message Routing Service
    Open Services console (services.msc) and look for a service related to Push Message Routing or Push Messaging, or run 'get-service | where-object {$_.DisplayName -like "*push*"}' in PowerShell
    Affected if The Push Message Routing Service is present and running on the system (vulnerability requires this component to be accessible)
  4. Verify authenticated local access capability
    Review local user accounts and permissions on the system using 'net user' in Command Prompt or check Group Policy settings under Local Policies > Security Options
    Affected if The system allows authenticated local user accounts (standard configuration for most Windows installations)

Your system is affected if it runs any of the listed Windows 10 or Windows 11 versions with a build number lower than the threshold AND the Push Message Routing Service is present and accessible to authenticated local users.

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.8957 / 10.0.17763.8511 / 10.0.19044.7058 or later
Fixed in 10.0.14393.895710.0.17763.851110.0.19044.7058
Interim mitigation

Apply vendor-provided security patches for the Push Message Routing Service and implement proper bounds checking in memory access operations.

Recommended fix High confidence

Upgrade to Windows 10 build 10.0.14393.8957 or later for 1607; 10.0.17763.8511 or later for 1809; 10.0.19044.7058 or later for 21h2; 10.0.19045.7058 or later for 22h2; Windows 11 build 10.0.22631.6783 or later for 23h2; 10.0.26100.7979 or later for 24h2; 10.0.26200.7979 or later for 25h2; 10.0.28000

  1. Open Windows Settings and navigate to Update & Security > Windows Update
  2. Click 'Check for updates' to download and install the latest security updates
  3. Alternatively, manually download and install the specific cumulative update for your Windows version that includes build 10.0.14393.8957 (Windows 10 1607), 10.0.17763.8511 (Windows 10 1809), 10.0.19044.7058 (Windows 10 21h2), 10.0.19045.7058 (Windows 10 22h2), 10.0.22631.6783 (Windows 11 23h2), 10.0.26100.7979 (Windows 11 24h2), 10.0.26200.7979 (Windows 11 25h2), or 10.0.28000.1719 (Windows 11 26h
  4. Restart the system after updates are installed to ensure the Push Message Routing Service patch is fully applied
  5. Verify the installed build number by running 'winver' command to confirm the fix is in place
Caveat Standard Windows updateapply risks - ensure backups exist and test in non-production environment first if possible

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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