Skip to content
vulnerability

CVE-2025-29824

7.8
High
KEV · Exploited in wildEPSS 19%Patch available

Use after free in Windows Common Log File System Driver allows an authorized attacker to elevate privileges locally.

exploited
Yes, in CISA KEV since 8 Apr 2025fix by 29 Apr 2025 (CISA deadline for US federal agencies)known use in ransomware campaignsunvetted proof-of-concept code on github
fix
Patch available see the advisory in the references
likelihood
EPSS 19.3%
Published 8 Apr 2025Analysed here 2 Nov 2026CVSS scored by the publisher (CNA)

do firstApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

triage
server-sideruntimeWAF can block: noAV · localCWE-416· Use After Free

Can a WAF block it? No. The attack needs local access to the machine, so a WAF is not on its path.

Also consider: patch

Based on the attack vector (local or physical access). We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

cvss vector
attack vectorlocalattack complexitylowprivileges requiredlowuser interactionnonescopeunchangedconfidentialityhighintegrityhighavailabilityhigh
CVSS 3.1 · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
common questions

Is CVE-2025-29824 being exploited?

Yes. CVE-2025-29824 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2025-29824?

CVE-2025-29824 is rated High with a CVSS score of 7.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2025-29824?

Yes. A fix has been recorded for CVE-2025-29824. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2025-29824 affect?

CVE-2025-29824 affects microsoft:windows_10_1507, microsoft:windows_10_1607, microsoft:windows_10_1809, microsoft:windows_10_21h2, and 11 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
microsoft:windows_10_1507microsoft:windows_10_1607microsoft:windows_10_1809microsoft:windows_10_21h2microsoft:windows_10_22h2microsoft:windows_11_22h2microsoft:windows_11_23h2microsoft:windows_11_24h2microsoft:windows_server_2008microsoft:windows_server_2012microsoft:windows_server_2016microsoft:windows_server_2019microsoft:windows_server_2022microsoft:windows_server_2022_23h2microsoft:windows_server_2025
affected versions
Microsoft Windows 10 Version 1507
  • affected>= 10.0.10240.0 and < 10.0.10240.20978
Microsoft Windows 10 Version 1607
  • affected>= 10.0.14393.0 and < 10.0.14393.7969
Microsoft Windows 10 Version 1809
  • affected>= 10.0.17763.0 and < 10.0.17763.7136
Microsoft Windows 10 Version 21H2
  • affected>= 10.0.19044.0 and < 10.0.19044.5737
Microsoft Windows 10 Version 22H2
  • affected>= 10.0.19045.0 and < 10.0.19045.5737
Microsoft Windows 11 version 22H2
  • affected>= 10.0.22621.0 and < 10.0.22621.5189
Microsoft Windows 11 version 22H3
  • affected>= 10.0.22631.0 and < 10.0.22631.5189
Microsoft Windows 11 Version 23H2
  • affected>= 10.0.22631.0 and < 10.0.22631.5189
Microsoft Windows 11 Version 24H2
  • affected>= 10.0.26100.0 and < 10.0.26100.3775
Microsoft Windows Server 2008 R2 Service Pack 1
  • affected>= 6.1.7601.0 and < 6.1.7601.27670
Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)
  • affected>= 6.1.7601.0 and < 6.1.7601.27670
Microsoft Windows Server 2008 Service Pack 2
  • affected>= 6.0.6003.0 and < 6.0.6003.23220
Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)
  • affected>= 6.0.6003.0 and < 6.0.6003.23220
Microsoft Windows Server 2012
  • affected>= 6.2.9200.0 and < 6.2.9200.25423
Microsoft Windows Server 2012 R2
  • affected>= 6.3.9600.0 and < 6.3.9600.22523
Microsoft Windows Server 2012 R2 (Server Core installation)
  • affected>= 6.3.9600.0 and < 6.3.9600.22523
Microsoft Windows Server 2012 (Server Core installation)
  • affected>= 6.2.9200.0 and < 6.2.9200.25423
Microsoft Windows Server 2016
  • affected>= 10.0.14393.0 and < 10.0.14393.7969
Microsoft Windows Server 2016 (Server Core installation)
  • affected>= 10.0.14393.0 and < 10.0.14393.7969
Microsoft Windows Server 2019
  • affected>= 10.0.17763.0 and < 10.0.17763.7136
Microsoft Windows Server 2019 (Server Core installation)
  • affected>= 10.0.17763.0 and < 10.0.17763.7136
Microsoft Windows Server 2022
  • affected>= 10.0.20348.0 and < 10.0.20348.3453
Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)
  • affected>= 10.0.25398.0 and < 10.0.25398.1551
Microsoft Windows Server 2025
  • affected>= 10.0.26100.0 and < 10.0.26100.3775
Microsoft Windows Server 2025 (Server Core installation)
  • affected>= 10.0.26100.0 and < 10.0.26100.3775

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

public exploits

Unvetted proof-of-concept code on GitHub: 4 GitHub proofs of concept

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

cisa ssvc

exploitation
active
automatable
no
technical impact
total

Assessed by CISA 8 Apr 2025 (SSVC 2.0.3).

timeline

  1. 8 Apr 2025Added to CISA KEV (exploited in the wild)
  2. 8 Apr 2025CISA SSVC assessment: exploitation active · 1 day later
  3. 8 Apr 2025Published · same day later
  4. 29 Apr 2025CISA remediation due date (US federal agencies) · 20 days later
  5. 14 May 2025First proof-of-concept repository on GitHub (unvetted) · 15 days later
  6. 10 Aug 2026CVE record last updated · 454 days (about 1 year) later
  7. 2 Nov 2026Analysed by vulneraibility.com · 84 days (about 3 months) later
how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
NVDCVE.orgCVE DetailsSource
4 references in the CVE record: 1 patch, 3 links
  • Patchmsrc.microsoft.com /update-guide/vulnerability/CVE-2025-29824
  • Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-29824
  • Linkvicarius.io /vsociety/posts/cve-2025-29824-windows-common-log-file-system-driver-elevation-o
  • Linkvicarius.io /vsociety/posts/cve-2025-29824-windows-common-log-file-system-driver-elevation-o

sources

  • CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
  • NVD: CVSS and CPE data
  • CISA KEV catalog: exploitation, date added, due date
  • CISA Vulnrichment (ADP): SSVC decision points
  • FIRST EPSS: exploit probability and percentile
  • PoC-in-GitHub: GitHub repositories that claim a proof of concept
  • Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved