# CVE-2025-24054: Microsoft Windows NTLM Hash Disclosure Spoofing

> An attacker can spoof network resources to disclose NTLM hashes, potentially enabling credential theft or authentication bypass on Windows systems.

- **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:** Yes, since 17 Apr 2025 (CISA KEV)
- **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-6v67-599p-fprc

## What is CVE-2025-24054?

CVE-2025-24054 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

External control of file name or path in Windows NTLM allows an unauthorized attacker to perform spoofing over a network.

Weakness: CWE-73 (External Control of File Name or Path)

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

It affects 15 products.


Products: Microsoft Windows 10 1507, Microsoft Windows 10 1607, Microsoft Windows 10 1809, Microsoft Windows 10 21h2, Microsoft Windows 10 22h2, Microsoft Windows 11 22h2, Microsoft Windows 11 23h2, Microsoft Windows 11 24h2, Microsoft Windows Server 2008, 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-24054?

No fix has been published for CVE-2025-24054 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 8 May 2025.

## Is CVE-2025-24054 being exploited?

Yes. Attackers have exploited CVE-2025-24054 in the wild since at least 17 Apr 2025.

Public exploit code:

- Proof of Concept for the NTLM Hash Leak via .library-ms CVE-2025-24054 / CVE-2025-24071 (github_poc): https://github.com/helidem/CVE-2025-24054_CVE-2025-24071-PoC
- PoC - CVE-2025-24071 / CVE-2025-24054, NTMLv2 hash'leri alınabilen bir vulnerability (github_poc): https://github.com/basekilll/CVE-2025-24054_PoC
- Windows File Explorer Zero Click NTLMv2-SSP Hash Disclosure (github_poc): https://github.com/Untouchable17/CVE-2025-24054
- Vulnerabilidad NTLM (CVE-2025-24054) explotada para robo de hashes (github_poc): https://github.com/moften/CVE-2025-24054
- Microsoft - NTLM Hash Disclosure Spoofing (library-ms) (exploitdb)
- https://github.com/S4mma3l/CVE-2025-24054 (github_poc): https://github.com/S4mma3l/CVE-2025-24054

## 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-24054 and fix it if it is affected.

What it is: CVE-2025-24054 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: Yes. Attackers have exploited CVE-2025-24054 in the wild since at least 17 Apr 2025.

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-24054/ (Markdown: https://insights.sbomify.com/CVE-2025-24054/index.md)
```

## Sources

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

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