cve.bz

CVE-2025-62221 Microsoft Windows Use After Free Vulnerability

7.8 highKEVEPSS 3.4%

High (7.8) in Microsoft Windows. In CISA KEV since 2025-12-09. EPSS 3.4% estimated probability of exploitation activity in the next 30 days.

On this page
Use after free in Windows Cloud Files Mini Filter Driver allows an authorized attacker to elevate privileges locally.

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
3.4% (up from 2.5% a week ago; 2.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 89th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA KEV
listed 2025-12-09, due 2025-12-30
CISA's assessment (SSVC)
Exploitation: active · Automatable: no · Technical impact: total, assessed 2025-12-10. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-416 Use After Free
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-62221 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-62221?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-62221?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-62221 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Microsoft Windows 10 Version 1809from 10.0.17763.0 before 10.0.17763.8146
Microsoft Windows 10 Version 21H2from 10.0.19044.0 before 10.0.19044.6691
Microsoft Windows 10 Version 22H2from 10.0.19045.0 before 10.0.19045.6691
Microsoft Windows 11 version 22H3from 10.0.22631.0 before 10.0.22631.6345
Microsoft Windows 11 Version 23H2from 10.0.22631.0 before 10.0.22631.6345
Microsoft Windows 11 Version 24H2from 10.0.26100.0 before 10.0.26100.7462
Microsoft Windows 11 Version 25H2from 10.0.26200.0 before 10.0.26200.7462
Microsoft Windows Server 2019from 10.0.17763.0 before 10.0.17763.8146
Microsoft Windows Server 2019 (Server Core installation)from 10.0.17763.0 before 10.0.17763.8146
Microsoft Windows Server 2022from 10.0.20348.0 before 10.0.20348.4529
Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)from 10.0.25398.0 before 10.0.25398.2025
Microsoft Windows Server 2025from 10.0.26100.0 before 10.0.26100.7462
Microsoft Windows Server 2025 (Server Core installation)from 10.0.26100.0 before 10.0.26100.7462

GitHub PoC (unverified)

Repositories on GitHub named after this CVE. Nobody has checked them and they are not scanned: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.

References

Check your stackJSON