CVE-2025-62464
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 · uneditedBuffer over-read in Windows Projected File System 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 confidenceBuffer over-read vulnerability in Windows Projected File System (ProjFS) kernel-mode driver enables a locally authenticated attacker to read beyond allocated memory boundaries and elevate privileges to SYSTEM level.
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< 10.0.17763.8146< 10.0.19044.6691< 10.0.19045.6691< 10.0.22631.6345< 10.0.26100.7392< 10.0.26200.7392< 10.0.17763.8146< 10.0.20348.4467CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/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 checksWork through these to decide whether this CVE applies to you.
-
Check Windows version and build numberOpen Command Prompt and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to obtain the full version and build numberAffected if The build number is lower than any of these thresholds: 17763.8146 (Win10 1809/Server 2019), 19044.6691 (Win10 21h2), 19045.6691 (Win10 22h2), 22631.6345 (Win11 23h2), 26100.7392 (Win11 24h2), 26200.7392 (Win11 25h2), or 20348.4467 (Server 2022)
-
Determine if Projected File System (ProjFS) feature is enabledCheck if the ProjFS Minirt or Windows Projected File System filter driver is loaded by running 'fltmc filters' in Command Prompt and looking for entries related to ProjFS or ProjectedFS, or check the registry under HKLM\SYSTEM\CurrentControlSet\Services\ProjectedFSFlt for existenceAffected if The ProjFS filter driver is present and loaded in the filesystem filter stack; if ProjFS is not installed or the driver is not loaded, the vulnerability does not apply
-
Verify ProjFS kernel-mode driver file versionLocate the ProjFS driver file (typically mrxdav.sys in System32\drivers or the ProjectedFS filter driver) and right-click to view Properties, or run 'driverquery /v | findstr /i mrxdav' or the relevant filter driver name to see the file versionAffected if The driver file version is older than the patched versions corresponding to the Windows build numbers listed in the affected versions (e.g., version lower than 10.0.17763.8146 for Windows 10 1809/Server 2019)
A user is affected if they are running a Windows version within the affected build ranges AND the Projected File System (ProjFS) kernel-mode driver is enabled or loaded on their system.
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.0.17763.814610.0.19044.669110.0.19045.6691
Apply Microsoft security update KBXXXXX (CVE-2025-62464) via Windows Update or enterprise patch management system; validate deployment and monitor for post-patch stability issues.
Install the Windows security update containing CVE-2025-62464 (released via Microsoft Update/WSUS) - target builds: 10.0.17763.8146 (1809/Server 2019), 10.0.19044.6691 (21h2), 10.0.19045.6691 (22h2), 10.0.22631.6345 (23h2), 10.0.26100.7392 (24h2), 10.0.26200.7392 (25h2), 10.0.20348.4467 (Server 2022
- Identify the current Windows build version by running 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"'
- Determine which Windows release (1809, 21h2, 22h2, 23h2, 24h2, 25h2, Server 2019, or Server 2022) matches your current build
- Open Windows Update by going to Settings > Update & Security > Windows Update, or use WSUS/Intune/SCCM for enterprise deployments
- Check for updates and install the cumulative security update that includes the fix for CVE-2025-62464
- Verify the update succeeded by checking the installed updates (run 'ms-settings:windowsupdate' and view update history)
- Confirm the build version matches or exceeds the fixed build: Windows 10 1809/Server 2019: 10.0.17763.8146 | Windows 10 21h2: 10.0.19044.6691 | Windows 10 22h2: 10.0.19045.6691 | Windows 11 23h2: 10.0.22631.6345 | Windows 11 24h2: 10.0.26100.7392 | Windows 11 25h2: 10.0.26200.7392 | Windows Server 2022: 10.0.20348.4467
- Restart the system as required to complete the installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2025-62464 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-62464 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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