dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-27741

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

A local privilege escalation vulnerability exists in Windows NTFS due to an out-of-bounds read condition. An unauthorized attacker can exploit this to elevate their privileges on the affected system, potentially gaining administrative or SYSTEM-level access.

MitigationApply the relevant Microsoft security update for Windows that addresses CVE-2025-27741. Prioritize patching systems where untrusted users have local access.

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 build version
    Open Command Prompt and run 'winver' to display the OS build number, or run 'systeminfo | findstr /C:"Build"' to get the exact build version in the format 10.0.xxxxx.yyyyy
    Affected if The build number falls below the fixed versions: 10.0.10240.20978 for 1507, 10.0.14393.7969 for 1607/Server 2016, 10.0.17763.7136 for 1809/Server 2019, or any build for Server 2008/2012 (all versions affected)
  2. Identify Windows edition and version
    Run 'winver' or check System Properties to confirm whether the system is Windows 10 1507, 1607, 1809, or Windows Server 2008, 2012, 2016, or 2019
    Affected if The system matches any of the affected Windows 10 versions or Windows Server versions listed in the affected products
  3. Verify NTFS file system is in use
    Open Command Prompt and run 'fsutil fsinfo volumeinfo C:' (or any local drive letter) to confirm the file system is NTFS
    Affected if The file system is NTFS (which is the default for all affected Windows versions)
  4. Confirm build via registry if needed
    Open Registry Editor and navigate to 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion', then check the 'CurrentBuild' and 'DisplayVersion' values
    Affected if The CurrentBuild number is lower than the thresholds listed in step 1 for the corresponding Windows version

A system is affected if it runs any of the listed Windows 10 or Windows Server versions with a build number below the specified thresholds, or runs all versions of Server 2008/2012, and uses NTFS as the file system.

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 Windows that addresses CVE-2025-27741. Prioritize patching systems where untrusted users have local access.

Recommended fix High confidence

Apply Microsoft security KB patch for CVE-2025-27741; for Windows Server 2008/2012 which are end-of-life, upgrade to a supported Windows Server version (2016, 2019, 2022)

  1. Identify the Windows version and build number by running 'winver' or 'systeminfo' in Command Prompt
  2. Navigate to the Microsoft Security Update Guide (msrc.microsoft.com) and search for CVE-2025-27741
  3. Download and install the specific KB patch corresponding to your Windows version and architecture
  4. Alternatively, run Windows Update and install all available security updates for this month
  5. After installation, restart the system to apply the patch
  6. Verify the update was installed by checking 'View update history' in Windows Update or by running 'systeminfo' to confirm the build number matches or exceeds the fixed version (10.0.10240.20978 for 1507, 10.0.14393.7969 for 1607/Server 2016, 10.0.17763.7136 for 1809/Server 2019)
Caveat Windows Server 2008 and 2012 are end-of-life with no further security patches; legacy applications may require testing on newer OS versions

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
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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