dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2025-62467

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
Integer overflow or wraparound 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 confidence

This is a local privilege escalation vulnerability in Windows Projected File System (ProjFS) caused by an integer overflow or wraparound condition. An authorized local attacker could exploit this to gain elevated privileges on the affected system. The vulnerability requires local access but does not require user interaction.

MitigationApply the Microsoft security update for CVE-2025-62467 once available through Windows Update or the Microsoft Security Update Guide. Prioritize patching systems where untrusted local users have 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 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. Identify Windows version and build number
    Run 'winver' from the command prompt or 'systeminfo' and locate the OS Name, Version, and Build number. Alternatively, run 'reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentBuild' to get the build number.
    Affected if The build number falls below any of these thresholds: 17763.8146, 19044.6691, 19045.6691, 22631.6345, 26100.7392, 26200.7392, or 20348.4467 depending on your Windows edition.
  2. Confirm Windows edition matches affected product list
    Run 'winver' or check systeminfo to identify your exact Windows edition (Windows 10 1809, Windows 10 21h2, Windows 10 22h2, Windows 11 23h2, Windows 11 24h2, Windows 11 25h2, Windows Server 2019, or Windows Server 2022).
    Affected if Your Windows edition and version combination is listed in the affected products but the build number is below the corresponding threshold.
  3. Determine if Projected File System (ProjFS) is enabled
    Run 'Get-WindowsOptionalFeature -Online -FeatureName *ProjFS*' in PowerShell with administrator privileges, or check via 'dism /online /get-features /featurename:ProjFS' from command prompt.
    Affected if ProjFS is enabled or the feature state shows as 'Enabled' on the system.
  4. Check for pending or installed security updates
    Run 'Get-HotFix | Where-Object {$_.Description -like "Security Update"} | Sort-Object InstalledOn -Descending | Select-Object -First 10' in PowerShell, or view the installed updates via 'appwiz.cpl' and look for recent security updates.
    Affected if No security update addressing CVE-2025-62467 is installed and your system meets the version conditions in steps 1 and 2.

Your system is affected if it runs a Windows version within the affected ranges AND has Projected File System (ProjFS) enabled AND lacks the security update for CVE-2025-62467.

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-62467 once available through Windows Update or the Microsoft Security Update Guide. Prioritize patching systems where untrusted local users have access.

Recommended fix High confidence

Install the Microsoft security update for CVE-2025-62467 (check Windows Update for the applicable KB article) - the fix brings affected builds to: 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 | W

  1. Identify the exact Windows version and build number by running 'winver' or 'systeminfo'
  2. Open Settings > Windows Update > Check for updates
  3. Install all available security updates, specifically looking for the KB article associated with CVE-2025-62467
  4. Restart the system after updates are installed
  5. Verify the update was applied by checking the installed updates list or running 'winver' to confirm the build number matches or exceeds the fixed version for your Windows release
Caveat Standard Windows security update - no breaking changes expected; apply all pending Windows Updates for comprehensive protection

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1809 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,080
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,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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