dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-26648

HIGH · 7.8 CVSS v3.1 Published 2025-04-08
Fix available
A fix is available. Upgrade to 10.0.10240.20978 / 10.0.14393.7969 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
Sensitive data storage in improperly locked memory in Windows Kernel 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 Windows Kernel vulnerability where sensitive data is stored in improperly locked memory, allowing a locally authorized attacker to escalate privileges. The flaw exists in how the Windows Kernel manages memory locking for sensitive information, potentially exposing credentials or other privileged data that could be exploited for local privilege escalation.

MitigationApply the Microsoft security update for CVE-2025-26648 immediately to all affected Windows systems. As a defense-in-depth measure, restrict local administrative privileges and monitor for suspicious processes accessing kernel memory.

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.20978
Windows 10 1607Operating system
Affected:< 10.0.14393.7969
Windows 10 1809Operating system
Affected:< 10.0.17763.7136
Windows 10 21h2Operating system
Affected:< 10.0.19044.5737
Windows 10 22h2Operating system
Affected:< 10.0.19045.5737
Windows 11 22h2Operating system
Affected:< 10.0.22621.5189
Windows 11 23h2Operating system
Affected:< 10.0.22631.5189
Windows 11 24h2Operating system
Affected:< 10.0.26100.3775

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 10 build version
    Open Command Prompt and run: winver OR systeminfo | findstr /B /C:"OS Version"
    Affected if The build number is less than 10.0.10240.20978 (1507), 10.0.14393.7969 (1607), 10.0.17763.7136 (1809), 10.0.19044.5737 (21h2), or 10.0.19045.5737 (22h2)
  2. Check Windows 11 build version
    Open Command Prompt and run: winver OR systeminfo | findstr /B /C:"OS Version"
    Affected if The build number is less than 10.0.22621.5189 (22h2), 10.0.22631.5189 (23h2), or 10.0.26100.3775 (24h2)
  3. Verify security update installation
    Open Settings > Windows Update > Update History, or run: wmic qfe list | findstr "KB..." (check for March 2025 or later kernel-related security updates)
    Affected if No security update containing CVE-2025-26648 fix (March 2025 patch Tuesday or later) is installed

You are affected if your Windows version matches any of the affected build ranges AND the CVE-2025-26648 security update is not installed.

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.20978 / 10.0.14393.7969 / 10.0.17763.7136 or later
Fixed in 10.0.10240.2097810.0.14393.796910.0.17763.7136
Interim mitigation

Apply the Microsoft security update for CVE-2025-26648 immediately to all affected Windows systems. As a defense-in-depth measure, restrict local administrative privileges and monitor for suspicious processes accessing kernel memory.

Recommended fix High confidence

Apply the March 2025 or later Windows Security Update (KB) containing the fix for CVE-2025-26648, which upgrades the OS build to one of: 10.0.10240.20978 (Win10 1507), 10.0.14393.7969 (Win10 1607), 10.0.17763.7136 (Win10 1809), 10.0.19044.5737 (Win10 21h2), 10.0.19045.5737 (Win10 22h2), 10.0.22621.5

  1. Open Settings > Update & Security > Windows Update
  2. Click 'Check for updates' to download and install the latest cumulative security update
  3. After installation, verify the OS build number matches or exceeds the fixed version for your Windows release
  4. Restart the computer as prompted to apply the kernel-level update
  5. Confirm the update was installed by checking Update History - look for the relevant KB patch in the list
Caveat None - this is a standard Microsoft security patch; no configuration or feature changes required

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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