Microsoft Windows Common Log File System (CLFS) Driver Use-After-Free Vulnerability
CVE-2025-29824 is a security vulnerability in Microsoft Windows, added to CISA KEV on April 8, 2025. Patch order: first of four. Known ransomware use: yes.
What is CVE-2025-29824?
Microsoft Windows Common Log File System (CLFS) Driver contains a use-after-free vulnerability that allows an authorized attacker to elevate privileges locally.
Known to be used in ransomware campaigns. Active threat actors have chained this vulnerability into ransomware operations — treat patching as a same-week priority, not a "next maintenance window" task. The fix is the same one below; the urgency is higher.
Who is affected by CVE-2025-29824?
Affects anyone running Windows workstations or servers. In a small CPA, legal, or dental practice, Windows is typically the platform your accounting, document management, or practice management software runs on — exploitation gives an attacker access to whatever client files and credentials live on those machines.
What should I do about CVE-2025-29824?
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
The action above is CISA's wording. The directive it names, BOD 22-01, was revoked by BOD 26-04 on June 10, 2026; CISA's catalog still carries the older text for this entry.
If you don't have someone in-house to verify the patch deployed across every endpoint — or you're not sure whether you're affected — that's exactly the kind of triage we do. Request a free review.
Insurance readiness
Your insurer will ask if this is patched.
Unpatched entries on CISA's Known Exploited Vulnerabilities list are exactly what cyber-insurance carrier questionnaires probe for, and knowing which controls they check is how you keep a renewal from stalling.
Get the free carrier questionnaire →Severity
CVSS base score: 7.8 — HIGH
Weakness classification: CWE-416
Microsoft fix
- KB5055519 (Security Update)
- KB5055526 (Security Update)
- KB5055518 (Security Update)
- KB5055528 (Security Update)
- KB5055523 (Security Update)
- KB5055527 (Security Update)
- KB5055547 (Security Update)
- KB5055521 (Security Update)
- KB5055609 (Monthly Rollup)
- KB5055596 (Security Only)
- KB5055561 (Monthly Rollup)
- KB5055570 (Security Only)
- KB5055581 (Monthly Rollup)
- KB5055557 (Monthly Rollup)
Microsoft Exploitability Index (assessed at update release): Exploitation Detected
Microsoft has confirmed in-the-wild exploitation in the latest software release. This aligns with CISA's listing of this CVE.
Vendor workaround
No vendor workaround published. Patching is the only fix.
CISA due date
CISA's listed due date: April 29, 2025.
Federal civilian agencies work under CISA's Binding Operational Directive 26-04, which replaced BOD 22-01 on June 10, 2026. It sets the deadline for each affected system by:
- How exposed that system is to the internet
- Whether the attack can be automated
- How much control it gives an attacker
Its table gives catalogued vulnerabilities 3 or 14 days.
None of this binds a private business, but treat the date as a strong recommendation, especially if you handle regulated data (HIPAA, GLBA, ABA model rules).
EPSS
EPSS score: 13.9% — higher than 96% of all scored CVEs.
EPSS estimates the probability of exploitation activity in the next 30 days. Every entry on this site is already confirmed exploited, so read it as relative urgency among the things you still have open, not as permission to wait.
Other exploited Microsoft Windows entries
More CISA KEV entries for Microsoft Windows. Same product line, same actively-exploited status.
Source
This entry comes from CISA's Known Exploited Vulnerabilities catalog, public US-Government data we pull daily. The plain-language framing and the what-to-do guidance above are ours. View the original entry on cisa.gov.