dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-27483

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 in the Windows NTFS driver allows a local attacker to read memory beyond allocated boundaries, which can be exploited to elevate privileges to SYSTEM level on the affected Windows system.

MitigationApply the Microsoft security update for CVE-2025-27483 to all affected Windows systems; prioritize endpoint patching and verify complete deployment across the environment.

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 2012Operating system
Affected:= 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
    Open Command Prompt and run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to display the installed Windows 10 build number
    Affected if The build number is less than 10.0.10240.20978 for 1507, less than 10.0.14393.7969 for 1607, or less than 10.0.17763.7136 for 1809
  2. Check Windows Server version and build
    Open Command Prompt and run 'systeminfo' or 'winver' to display the Windows Server version and build number
    Affected if The system is Windows Server 2016 with build < 10.0.14393.7969, Windows Server 2019 with build < 10.0.17763.7136, or Windows Server 2012 R2 specifically
  3. Confirm Windows edition for Server 2012 R2
    Run 'systeminfo' and examine the OS Name or run 'winver' to verify the exact Windows Server 2012 edition
    Affected if The system is Windows Server 2012 R2 (not earlier 2012 versions) - this edition is specifically affected regardless of build within that version
  4. Verify NTFS driver is loaded
    Run 'sc query ntfs' or check Device Manager for NTFS.sys driver status - the vulnerability exists in the NTFS driver component
    Affected if The NTFS driver is present and loaded, which is the default state for any Windows system using NTFS file system

You are affected if your Windows version matches any of the specified builds: Windows 10 1507/1607/1809 below their thresholds, Windows Server 2012 R2, or Windows Server 2016/2019 below their thresholds.

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-27483 to all affected Windows systems; prioritize endpoint patching and verify complete deployment across the environment.

Recommended fix High confidence
  1. Identify the current Windows build version by running 'winver' or 'systeminfo' in Command Prompt
  2. Determine which Windows 10 or Windows Server version is installed and note the current build number
  3. Open Windows Update by going to Settings > Update & Security > Windows Update
  4. Click 'Check for updates' to retrieve the latest security patches
  5. Install all available updates, specifically looking for the security update that addresses this vulnerability (CVE-2025-27483)
  6. Restart the computer after the updates are installed
  7. Verify the installation was successful by checking that the build number matches or exceeds the fixed version for your Windows release

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
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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