dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-27468

HIGH · 7.0 CVSS v3.1 Published 2025-05-13
Fix available
A fix is available. Upgrade to 10.0.10240.21014 / 10.0.14393.8066 or later.
See remediation →
72/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
Improper privilege management in Windows Secure Kernel Mode 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

Improper privilege management in Windows Secure Kernel Mode allows a local authorized attacker to elevate privileges. This vulnerability exists in the secure kernel isolation layer, potentially allowing an attacker with existing local access to bypass security boundaries and gain higher-level system privileges.

MitigationApply Microsoft security updates for Windows Secure Kernel Mode once available. Prioritize patching systems with higher privilege users or external-facing services.

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.21014
Windows 10 1607Operating system
Affected:< 10.0.14393.8066
Windows 10 1809Operating system
Affected:< 10.0.17763.7314
Windows 10 21h2Operating system
Affected:< 10.0.19044.5854
Windows 10 22h2Operating system
Affected:< 10.0.19045.5854
Windows 11 22h2Operating system
Affected:< 10.0.22621.5335
Windows 11 23h2Operating system
Affected:< 10.0.22631.5335
Windows 11 24h2Operating system
Affected:< 10.0.26100.4061

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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/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. Retrieve Windows build number
    Open Command Prompt and run 'ver' or 'systeminfo | findstr /B /C:"OS Version"' to display the installed Windows build number
    Affected if The displayed build number is lower than any of these thresholds: 10240.21014 (Win10 1507), 14393.8066 (Win10 1607), 17763.7314 (Win10 1809), 19044.5854 (Win10 21h2/22h2), 22621.5335 (Win11 22h2), 22631.5335 (Win11 23h2), or 26100.4061 (Win11 24h2)
  2. Identify Windows release
    Run 'winver' or check System Properties to confirm whether the system is Windows 10 version 1507, 1607, 1809, 21h2, 22h2, or Windows 11 version 22h2, 23h2, or 24h2
    Affected if The system runs any of the listed Windows 10 or Windows 11 versions and the build number falls below the corresponding threshold in the affected version list

A system is affected if it runs any of the specified Windows 10 or Windows 11 versions with a build number lower than the fixed version for that release branch, since the vulnerability exists in the Secure Kernel Mode component present in these Windows versions.

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.21014 / 10.0.14393.8066 / 10.0.17763.7314 or later
Fixed in 10.0.10240.2101410.0.14393.806610.0.17763.7314
Interim mitigation

Apply Microsoft security updates for Windows Secure Kernel Mode once available. Prioritize patching systems with higher privilege users or external-facing services.

Recommended fix High confidence

Windows 10 1507: 10.0.10240.21014 | Windows 10 1607: 10.0.14393.8066 | Windows 10 1809: 10.0.17763.7314 | Windows 10 21h2: 10.0.19044.5854 | Windows 10 22h2: 10.0.19045.5854 | Windows 11 22h2: 10.0.22621.5335 | Windows 11 23h2: 10.0.22631.5335 | Windows 11 24h2: 10.0.26100.4061

  1. Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Open Settings > Windows Update or run 'ms-settings:windowsupdate'
  3. Check for and install the latest cumulative security update for your Windows version
  4. Alternatively, download the specific security update from Microsoft Update Catalog (search for the KB article associated with CVE-2025-27468)
  5. Restart the computer after the update is installed
  6. Verify the patch was applied by checking the installed updates or running 'systeminfo' to confirm the build number matches or exceeds the fixed version for your Windows release
Caveat Standard Windows update risks apply - ensure backups and compatibility testing for business-critical applications before deploying broadly

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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