CVE-2025-24071
Exposure of sensitive information to an unauthorized actor in Windows File Explorer allows an unauthorized attacker to perform spoofing over a network.
- CVSS
- 6.5Mediumscored by the publisher (CNA)
- Exploited in the wild
- Not knownPublic exploit code; not in CISA KEV
- EPSS
- 23.3%chance of exploitation in the next 30 daystop 3% of scored CVEsFIRST score of 11 Nov 2026
- Fix
- Patch availablesee the advisories in the references
- Published
- 11 Mar 2025analysed here 12 Nov 2026
Summary
Triage
The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.
Affected products
| Product | Affected versions | Vendor says fixed in |
|---|---|---|
| Microsoft Windows 10 Version 1507 | >= 10.0.10240.0 and < 10.0.10240.20947Vendor says fixed in: not stated | |
| Microsoft Windows 10 Version 1607 | >= 10.0.14393.0 and < 10.0.14393.7876Vendor says fixed in: not stated | |
| Microsoft Windows 10 Version 1809 | >= 10.0.17763.0 and < 10.0.17763.7009Vendor says fixed in: not stated | |
| Microsoft Windows 10 Version 21H2 | >= 10.0.19044.0 and < 10.0.19044.5608Vendor says fixed in: not stated | |
| Microsoft Windows 10 Version 22H2 | >= 10.0.19045.0 and < 10.0.19045.5608Vendor says fixed in: not stated | |
| Microsoft Windows 11 version 22H2 | >= 10.0.22621.0 and < 10.0.22621.5039Vendor says fixed in: not stated | |
| Microsoft Windows 11 version 22H3 | >= 10.0.22631.0 and < 10.0.22631.5039Vendor says fixed in: not stated | |
| Microsoft Windows 11 Version 23H2 | >= 10.0.22631.0 and < 10.0.22631.5039Vendor says fixed in: not stated | |
| Microsoft Windows 11 Version 24H2 | >= 10.0.26100.0 and < 10.0.26100.3476Vendor says fixed in: not stated | |
| Microsoft Windows Server 2012 R2 | >= 6.3.9600.0 and < 6.3.9600.22470Vendor says fixed in: not stated | |
| Microsoft Windows Server 2012 R2 (Server Core installation) | >= 6.3.9600.0 and < 6.3.9600.22470Vendor says fixed in: not stated | |
| Microsoft Windows Server 2016 | >= 10.0.14393.0 and < 10.0.14393.7876Vendor says fixed in: not stated | |
| Microsoft Windows Server 2016 (Server Core installation) | >= 10.0.14393.0 and < 10.0.14393.7876Vendor says fixed in: not stated | |
| Microsoft Windows Server 2019 | >= 10.0.17763.0 and < 10.0.17763.7009Vendor says fixed in: not stated | |
| Microsoft Windows Server 2019 (Server Core installation) | >= 10.0.17763.0 and < 10.0.17763.7009Vendor says fixed in: not stated | |
| Microsoft Windows Server 2022 | >= 10.0.20348.0 and < 10.0.20348.3328Vendor says fixed in: not stated | |
| Microsoft Windows Server 2022, 23H2 Edition (Server Core installation) | >= 10.0.25398.0 and < 10.0.25398.1486Vendor says fixed in: not stated | |
| Microsoft Windows Server 2025 | >= 10.0.26100.0 and < 10.0.26100.3476Vendor says fixed in: not stated | |
| Microsoft Windows Server 2025 (Server Core installation) | >= 10.0.26100.0 and < 10.0.26100.3476Vendor says fixed in: not stated |
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.
Products named in our analysis
- microsoft:windows_10_1507
- microsoft:windows_10_1607
- microsoft:windows_10_1809
- microsoft:windows_11_23h2
- microsoft:windows_11_24h2
- microsoft:windows_server_2012
- microsoft:windows_server_2016
- microsoft:windows_server_2019
- microsoft:windows_server_2022
- microsoft:windows_server_2022_23h2
- microsoft:windows_server_2025
Fix and mitigation
WAF and other mitigations
Can a WAF block it? Partly. Information exposure: some WAFs can scan responses and hide known leak patterns, such as stack traces or keys.
Also consider: response filtering
Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Remediation steps (AI-written)
Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.
Exploitation evidence
- CISA KEV catalog
- Not listed as of our last sync.
- Public exploit code
- Yes: 2 on Exploit-DB · 23 GitHub proofs of concept
- CISA SSVC
- exploitation none, automatable yes, technical impact partialAssessed by CISA 11 Mar 2025 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.
Exploit-DB
- Windows File Explorer Windows 10 Pro x64 - TAR Extractionremote, 13 Jun 2025
- Windows File Explorer Windows 11 (23H2) - NTLM Hash Disclosureremote, 29 May 2025
GitHub proofs of concept
- 0x6rss/CVE-2025-24071_PoC415 stars
- ThemeHackers/CVE-2025-2407134 stars
- FOLKS-iwd/CVE-2025-24071-msfvenom25 stars
- Marcejr117/CVE-2025-24071_PoC24 stars
and 19 more repositories
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.
Timeline
- 11 Mar 2025Published
- 11 Mar 2025CISA SSVC assessment: exploitation nonesame day later
- 16 Mar 2025First public exploit or proof of concept4 days later
- 13 Feb 2026CVE record last updated335 days (about 11 months) later
- 12 Nov 2026Analysed by vulneraibility.com272 days (about 9 months) later
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
| Metric | Value | What it means |
|---|---|---|
| Attack vector | NetworkReachable over the internet or any routable network. | Reachable over the internet or any routable network. |
| Attack complexity | LowRepeatable attack, no special conditions. | Repeatable attack, no special conditions. |
| Privileges required | NoneThe attacker needs no prior access. | The attacker needs no prior access. |
| User interaction | RequiredA victim must click, open or otherwise cooperate. | A victim must click, open or otherwise cooperate. |
| Scope | UnchangedImpact stays within the vulnerable component. | Impact stays within the vulnerable component. |
| Confidentiality | HighTotal data disclosure possible. | Total data disclosure possible. |
| Integrity | NoneNo unauthorised modification. | No unauthorised modification. |
| Availability | NoneThe service stays up. | The service stays up. |
Common questions
Is CVE-2025-24071 being exploited?
Not confirmed. CVE-2025-24071 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 23% probability of exploitation in the next 30 days.
How severe is CVE-2025-24071?
CVE-2025-24071 is rated Medium with a CVSS score of 6.5. 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-24071?
Yes. A fix has been recorded for CVE-2025-24071. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2025-24071 affect?
CVE-2025-24071 affects microsoft:windows_10_1507, microsoft:windows_10_1607, microsoft:windows_10_1809, microsoft:windows_11_23h2, and 7 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.
References
3 references in the CVE record, grouped by the tags the record gives them.
Patches (1)
- msrc.microsoft.com /update-guide/vulnerability/CVE-2025-24071
Other links (2)
- vicarius.io /vsociety/posts/cve-2025-24071-spoofing-vulnerability-in-microsoft-windows-file-
- vicarius.io /vsociety/posts/cve-2025-24071-spoofing-vulnerability-in-microsoft-windows-file-
Where the data on this page comes from
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Exploit-DB: published exploits
- 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.
Similar CVEs
Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.