dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-27733

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 →
81/100
Remediation priority · High
No privileges

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 Windows NTFS allows an unauthorized 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

An out-of-bounds read vulnerability exists in Windows NTFS (the default Windows file system) that allows a local unauthorized attacker to read memory beyond intended boundaries, leading to local privilege escalation from a standard user to elevated (administrator or SYSTEM) privileges.

MitigationApply the relevant Microsoft security update for CVE-2025-27733 through Windows Update or your patch management system. Until patched, limit local access to trusted users and monitor for suspicious processes.

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 Server 2008Operating system
Affected:all versions= r2
Windows Server 2012Operating system
Affected:all versions= r2
Windows Server 2016Operating system
Affected:< 10.0.14393.7969
Windows Server 2019Operating system
Affected:< 10.0.17763.7136

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

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' and note the full build number (e.g., 10.0.10240.xxxxx)
    Affected if Build is below 10.0.10240.20978 for 1507, below 10.0.14393.7969 for 1607, or below 10.0.17763.7136 for 1809
  2. Check Windows Server version
    Run 'systeminfo' or 'winver' and identify the server version and build number
    Affected if Running Windows Server 2008 or Server 2012 (any build), or Server 2016 below 10.0.14393.7969, or Server 2019 below 10.0.17763.7136
  3. Confirm NTFS filesystem is in use
    Run 'fsutil fsinfo volumeinfo C:' and check the 'File System Name' field, or right-click the system drive in File Explorer and view Properties
    Affected if The filesystem is NTFS (this is the default and required condition for the vulnerability)
  4. Verify current user context
    Run 'whoami /groups' to see current user privileges
    Affected if Running as a standard (non-admin) user and the system version is in the vulnerable range

If the Windows build number falls below the specified thresholds for your version (or is any version of Server 2008/2012), and NTFS is in use, the system is vulnerable to local privilege escalation via this NTFS flaw.

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 relevant Microsoft security update for CVE-2025-27733 through Windows Update or your patch management system. Until patched, limit local access to trusted users and monitor for suspicious processes.

Recommended fix High confidence

Windows 10 1507: upgrade to 10.0.10240.20978 or later | Windows 10 1607: upgrade to 10.0.14393.7969 or later | Windows 10 1809: upgrade to 10.0.17763.7136 or later | Windows Server 2016: upgrade to 10.0.14393.7969 or later | Windows Server 2019: upgrade to 10.0.17763.7136 or later | Windows Server 2

  1. Check current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Identify which affected version range your system falls into from the list: Windows 10 1507/1607/1809, Windows Server 2008/2012/2016/2019
  3. For Windows 10 systems: Apply the relevant cumulative update that includes the fix for CVE-2025-27733 (KB number as published in the corresponding Microsoft Security Update Guide)
  4. For Windows Server systems: Apply the relevant monthly cumulative update or security-only update from Microsoft Update Catalog
  5. Restart the system after applying the update
  6. Verify the installed updates by checking 'Installed Updates' in Control Panel or running 'Get-HotFix' in PowerShell
Caveat Windows Server 2008 and 2012 are end-of-life with no further security updates; migration to supported OS required; legacy application compatibility should be tested before applying updates to older Windows 10 versions

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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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