# CVE-2025-24071: Microsoft Windows File Explorer Spoofing Vulnerability

> An attacker can exploit Windows File Explorer to expose sensitive information and perform spoofing attacks over the network.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N/E:U/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Mar 2025
- **Updated:** 13 Feb 2026
- **Also known as:** GHSA-mppc-8qxh-4wjw

## What is CVE-2025-24071?

CVE-2025-24071 is a medium-severity vulnerability in Microsoft Windows 10 1507, published on 11 Mar 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Exposure of sensitive information to an unauthorized actor in Windows File Explorer allows an unauthorized attacker to perform spoofing over a network.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2025-24071?

It affects 11 products.


Products: 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.

## How do I fix CVE-2025-24071?

No fix has been published for CVE-2025-24071 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-24071 being exploited?

There is no known exploitation of CVE-2025-24071 in the wild and no public exploit code.

Public exploit code:

- CVE-2025-24071: NTLM Hash Leak via RAR/ZIP Extraction and .library-ms File (github_poc): https://github.com/0x6rss/CVE-2025-24071_PoC
- Windows File Explorer Spoofing Vulnerability (CVE-2025-24071) (github_poc): https://github.com/ThemeHackers/CVE-2025-24071
- Metasploit module for CVE-2025-24071 - Windows NTLM Hash Leak via .library-ms (github_poc): https://github.com/FOLKS-iwd/CVE-2025-24071-msfvenom
- A PoC of CVE-2025-24071 / CVE-2025-24054, A windows vulnerability that allow get NTMLv2 hashes (github_poc): https://github.com/Marcejr117/CVE-2025-24071_PoC
- Exploited CVE-2025-24071 via SMB by hosting a .library-ms file inside a .tar archive. Using tar x from smbclient, the payload is extracted server-side without user interaction. Responder captures the NTLM hash once the target accesses the library. (github_poc): https://github.com/ex-cal1bur/SMB_CVE-2025-24071
- CVE-2025-24071 Proof Of Concept (github_poc): https://github.com/LOOKY243/CVE-2025-24071-PoC

## Other vulnerabilities in Microsoft Windows 10 1507

- [CVE-2017-8543](https://insights.sbomify.com/CVE-2017-8543/): Microsoft Windows Search Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2025-33053](https://insights.sbomify.com/CVE-2025-33053/): Microsoft Windows External Control of File Name or Path (high 8.8, exploited in the wild)
- [CVE-2025-33073](https://insights.sbomify.com/CVE-2025-33073/): Microsoft Windows SMB Client Improper Access Control (high 8.8, exploited in the wild)
- [CVE-2024-49039](https://insights.sbomify.com/CVE-2024-49039/): Microsoft Windows Task Scheduler Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2024-43461](https://insights.sbomify.com/CVE-2024-43461/): Microsoft Windows MSHTML Platform Spoofing (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-24071 and fix it if it is affected.

What it is: CVE-2025-24071 is a medium-severity vulnerability in Microsoft Windows 10 1507, published on 11 Mar 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-24071 in the wild and no public exploit code.

Affected product: Microsoft Windows 10 1507. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-24071/ (Markdown: https://insights.sbomify.com/CVE-2025-24071/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-24071
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-24071
- OSV: https://osv.dev/vulnerability/CVE-2025-24071

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-24071/
Summaries are generated and may contain mistakes; the official description above is the record.