dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2025-62461

HIGH · 7.8 CVSS v3.1 Published 2025-12-09
Fix available
A fix is available. Upgrade to 10.0.17763.8146 / 10.0.19044.6691 or later.
See remediation →
80/100
Remediation priority · High
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
Buffer over-read in Windows Projected File System Filter Driver 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 confidence

A buffer over-read vulnerability in the Windows Projected File System Filter Driver (ProjFS) allows a local authenticated attacker to read beyond allocated buffer boundaries in kernel memory, potentially exposing sensitive data and enabling elevation of privileges to SYSTEM level.

MitigationApply the Microsoft security update for CVE-2025-62461 as soon as feasible, and verify that the Projected File System functionality operates normally after patching.

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 1809Operating system
Affected:< 10.0.17763.8146
Windows 10 21h2Operating system
Affected:< 10.0.19044.6691
Windows 10 22h2Operating system
Affected:< 10.0.19045.6691
Windows 11 23h2Operating system
Affected:< 10.0.22631.6345
Windows 11 24h2Operating system
Affected:< 10.0.26100.7392
Windows 11 25h2Operating system
Affected:< 10.0.26200.7392
Windows Server 2019Operating system
Affected:< 10.0.17763.8146
Windows Server 2022Operating system
Affected:< 10.0.20348.4467

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Windows build version
    Run 'winver' or 'systeminfo' and note the full build number (for example, 10.0.19045.xxxx). Compare this against the vulnerable thresholds: 17763.8146 for Windows 10 1809/Server 2019; 19044.6691 for Windows 10 21h2; 19045.6691 for Windows 10 22h2; 22631.6345 for Windows 11 23h2; 26100.7392 for Windows 11 24h2; 26200.7392 for Windows 11 25h2; 20348.4467 for Windows Server 2022
    Affected if Your installed build number is lower than the threshold for your specific Windows version or edition
  2. Confirm ProjFS filter driver is present
    Run 'fltmc filters' from an elevated command prompt to list loaded filter drivers, or check the registry key 'HKLM\SYSTEM\CurrentControlSet\Services\ProjFS' to verify the driver service exists
    Affected if The ProjFS filter driver is registered on the system (service exists even if not actively attached to a volume)
  3. Identify active ProjFS instances
    Run 'fltmc filters' and look for any volumes with the 'ProjFS' filter attached, or query for active provider instances using 'fltregisteryinfo' if available
    Affected if Any volume has the Projected File System filter actively attached

You are affected if your Windows build is below the version threshold AND the ProjFS filter driver is present on the system, regardless of whether it is actively attached to volumes.

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.17763.8146 / 10.0.19044.6691 / 10.0.19045.6691 or later
Fixed in 10.0.17763.814610.0.19044.669110.0.19045.6691
Interim mitigation

Apply the Microsoft security update for CVE-2025-62461 as soon as feasible, and verify that the Projected File System functionality operates normally after patching.

Recommended fix High confidence

Windows 10 1809: 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 2019: 10.0.17763.8146 | Windows Server 2022: 10.0.20348.4467

  1. Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Determine if your current build number is below the fixed version for your Windows release
  3. Open Settings > Windows Update > Check for updates
  4. Install all available security updates, which will include the fix for this vulnerability
  5. Alternatively, manually install the specific security update from Microsoft Update Catalog matching your Windows version (search for the CVE number or the KB article for this vulnerability)
  6. Restart the system after updates are installed
  7. Verify the fix by checking that the build number now meets 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 1809 Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,520
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,432.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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