dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-27732

HIGH · 7.0 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 →
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
Sensitive data storage in improperly locked memory in Windows Win32K - GRFX 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 · high confidence

This is a local privilege escalation vulnerability in the Windows Win32K graphics subsystem (GRFX). The flaw involves sensitive data being stored in memory that is improperly locked, allowing an authorized attacker to potentially access or manipulate this data to elevate their privileges from a standard user to higher-level system access.

MitigationApply the Microsoft security update for CVE-2025-27732 as part of the regular Patch Tuesday cycle or emergency deployment if warranted. Prioritize endpoints with direct user access where local attackers could exploit this vulnerability.

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
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. Identify Windows version and build number
    Run 'winver' from command prompt or check System Properties, or run 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"'
    Affected if The displayed version falls within any of the affected build ranges listed in the CVE
  2. Obtain exact build number for precise comparison
    Run 'reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentBuild' and 'reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentBuildNumber' to get the numeric build
    Affected if The build number is lower than the minimum fixed build for your Windows release
  3. Verify Win32K subsystem is in use
    This is a kernel component that is always loaded on affected Windows systems with GUI; no specific configuration check needed - the vulnerability exists in the Win32K graphics subsystem (win32k.sys)
    Affected if Running any affected Windows version with graphical interface enabled
  4. Confirm no emergency or out-of-band patch has been applied
    Check installed updates via 'Get-HotFix' PowerShell cmdlet or view Windows Update history for security updates released after March 2025
    Affected if The system is missing the CVE-2025-27732 security update and version check shows vulnerable build

The system is affected if it runs any Windows 10 version (1507 through 22h2) or Windows 11 version (22h2 through 24h2) with a build number lower than the respective fixed build for that release, and the March 2025 security update has not been 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-27732 as part of the regular Patch Tuesday cycle or emergency deployment if warranted. Prioritize endpoints with direct user access where local attackers could exploit this vulnerability.

Recommended fix High confidence

Windows 10 1507: 10.0.10240.20978 | Windows 10 1607: 10.0.14393.7969 | Windows 10 1809: 10.0.17763.7136 | Windows 10 21h2: 10.0.19044.5737 | Windows 10 22h2: 10.0.19045.5737 | Windows 11 22h2: 10.0.22621.5189 | Windows 11 23h2: 10.0.22631.5189 | Windows 11 24h2: 10.0.26100.3775

  1. Open Windows Update settings and check for available updates
  2. Install all pending Windows security updates, specifically looking for the update addressing CVE-2025-27732
  3. After the update installs, restart the computer as prompted
  4. Verify the update was installed successfully by checking Windows Update history for the security patch
Caveat No expected breaking changes; a system restart is required after applying the security update

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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