CVE-2025-24071

HIGHNVD 6.57.5▲
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2025-03-11. NVD baseline CVSS 6.5; sources differ by 1.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
7.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 23%CVSS: 6.5Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

CVSS v3
6.5
EG Score
7.5(medium)
EG Risk
65(Track)
EG Risk 65/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
23%
EPSS %ILE
98%
KEV
Not listed

Published

March 11, 2025

Last Modified

July 3, 2025

References (3)

Vendor Advisories for CVE-2025-24071(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 4× in last 7d / 24× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 124 total refreshes for this CVE.

  1. 2026-09-24 14:02 UTCEPSS rescore
  2. 2026-09-23 13:46 UTCEPSS rescore
  3. 2026-09-22 14:47 UTCEPSS rescore
  4. 2026-09-18 19:27 UTCEPSS rescore
  5. 2026-09-16 14:06 UTCEPSS rescore
  6. 2026-09-16 05:13 UTCEPSS rescore
  7. 2026-09-15 03:09 UTCEPSS rescore
  8. 2026-09-12 15:00 UTCEPSS rescore
  9. 2026-09-11 14:51 UTCEPSS rescore
  10. 2026-09-11 09:35 UTCEPSS rescore
  11. 2026-09-10 09:33 UTCEPSS rescore
  12. 2026-09-08 21:59 UTCEPSS rescore
  13. 2026-09-07 16:00 UTCEPSS rescore
  14. 2026-09-06 13:46 UTCEPSS rescore
  15. 2026-09-06 13:46 UTCEPSS rescore
  16. 2026-09-05 15:28 UTCEPSS rescore
  17. 2026-09-04 05:05 UTCEPSS rescore
  18. 2026-09-02 14:11 UTCEPSS rescore
  19. 2026-09-01 13:52 UTCEPSS rescore
  20. 2026-09-01 04:38 UTCEPSS rescore
  21. 2026-08-30 19:16 UTCEPSS rescore
  22. 2026-08-30 01:21 UTCEPSS rescore
  23. 2026-08-28 21:40 UTCEPSS rescore
  24. 2026-08-27 14:24 UTCEPSS rescore
  25. 2026-08-25 13:47 UTCEPSS rescore
Show 75 more
  1. 2026-08-23 00:18 UTCEPSS rescore
  2. 2026-08-21 23:48 UTCEPSS rescore
  3. 2026-08-20 22:54 UTCEPSS rescore
  4. 2026-08-19 17:03 UTCEPSS rescore
  5. 2026-08-18 13:47 UTCEPSS rescore
  6. 2026-08-16 14:55 UTCEPSS rescore
  7. 2026-08-16 02:13 UTCEPSS rescore
  8. 2026-08-16 02:13 UTCEPSS rescore
  9. 2026-08-15 01:29 UTCEPSS rescore
  10. 2026-08-13 21:59 UTCEPSS rescore
  11. 2026-08-12 13:50 UTCEPSS rescore
  12. 2026-08-10 23:59 UTCEPSS rescore
  13. 2026-08-07 16:26 UTCEPSS rescore
  14. 2026-08-06 13:46 UTCEPSS rescore
  15. 2026-08-05 19:16 UTCEPSS rescore
  16. 2026-08-04 15:09 UTCEPSS rescore
  17. 2026-08-01 04:15 UTCEPSS rescore
  18. 2026-07-30 16:27 UTCEPSS rescore
  19. 2026-07-30 01:29 UTCEPSS rescore
  20. 2026-07-28 15:35 UTCEPSS rescore
  21. 2026-07-27 14:12 UTCEPSS rescore
  22. 2026-07-26 14:53 UTCEPSS rescore
  23. 2026-07-25 14:17 UTCEPSS rescore
  24. 2026-07-24 14:17 UTCEPSS rescore
  25. 2026-07-23 14:17 UTCEPSS rescore
  26. 2026-07-23 02:51 UTCEG score recompute
  27. 2026-07-22 14:07 UTCEPSS rescore
  28. 2026-07-22 14:07 UTCEPSS rescore
  29. 2026-07-21 15:24 UTCEPSS rescore
  30. 2026-07-20 17:07 UTCEPSS rescore
  31. 2026-07-19 02:28 UTCEPSS rescore
  32. 2026-07-19 02:28 UTCEPSS rescore
  33. 2026-07-18 10:03 UTCEPSS rescore
  34. 2026-07-16 17:02 UTCEPSS rescore
  35. 2026-07-15 16:57 UTCEPSS rescore
  36. 2026-07-15 16:57 UTCEPSS rescore
  37. 2026-07-15 01:59 UTCEPSS rescore
  38. 2026-07-13 22:29 UTCEPSS rescore
  39. 2026-07-13 22:29 UTCEPSS rescore
  40. 2026-07-12 05:46 UTCEPSS rescore
  41. 2026-07-12 05:46 UTCEPSS rescore
  42. 2026-07-11 08:27 UTCEPSS rescore
  43. 2026-07-11 08:26 UTCEPSS rescore
  44. 2026-07-09 19:09 UTCEPSS rescore
  45. 2026-07-08 15:14 UTCEPSS rescore
  46. 2026-07-06 16:26 UTCEPSS rescore
  47. 2026-07-05 02:30 UTCEPSS rescore
  48. 2026-07-04 06:30 UTCEPSS rescore
  49. 2026-07-01 15:06 UTCEPSS rescore
  50. 2026-06-30 23:21 UTCEPSS rescore
  51. 2026-06-30 23:21 UTCEPSS rescore
  52. 2026-06-28 14:07 UTCEPSS rescore
  53. 2026-06-28 14:07 UTCEPSS rescore
  54. 2026-06-28 04:55 UTCEPSS rescore
  55. 2026-06-28 04:55 UTCEPSS rescore
  56. 2026-06-27 03:08 UTCEPSS rescore
  57. 2026-06-27 03:08 UTCEPSS rescore
  58. 2026-06-25 13:49 UTCEPSS rescore
  59. 2026-06-25 13:49 UTCEPSS rescore
  60. 2026-06-24 14:04 UTCEPSS rescore
  61. 2026-06-24 14:04 UTCEPSS rescore
  62. 2026-06-23 21:32 UTCEPSS rescore
  63. 2026-06-23 21:32 UTCEPSS rescore
  64. 2026-06-22 14:25 UTCEPSS rescore
  65. 2026-06-22 14:25 UTCEPSS rescore
  66. 2026-06-21 14:56 UTCEPSS rescore
  67. 2026-06-21 14:56 UTCEPSS rescore
  68. 2026-06-21 01:59 UTCEPSS rescore
  69. 2026-06-21 01:59 UTCEPSS rescore
  70. 2026-06-18 17:52 UTCEPSS rescore
  71. 2026-06-18 17:52 UTCEPSS rescore
  72. 2026-06-17 17:52 UTCEPSS rescore
  73. 2026-06-16 17:52 UTCEPSS rescore
  74. 2026-06-16 17:52 UTCEPSS rescore
  75. 2026-06-15 17:48 UTCEPSS rescore

Publicly available exploits

(10 references)

Working exploit code is in the public domain (8 GitHub PoCs) (2 Exploit-DB entries). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCfsoc-ghost-0x/Fsociety-CVE-2025-24071-NTLM-Coercion
    First seen Dec 21, 2025

    Hello friend. This is the Fsociety Exploit Framework for CVE-2025-24071. Generates malicious .library-ms files to steal NTLMv2 hashes. Includes a 'Living Terminal' Cinematic Mode, Deep Trace logging, and stealth evasion techniques. Join the revolution. #Hacking #Exploit #CVE-2025-24071

    Open source ↗
  • Exploit-DBEDB-52325
    First seen Jun 13, 2025

    Windows File Explorer Windows 10 Pro x64 - TAR Extraction

    Open source ↗
  • GitHub PoCTH-SecForge/CVE-2025-24071
    First seen Jun 9, 2025

    Security Vulnerability Report: CVE-2025-24071 - Windows File Explorer Spoofing Vulnerability

    Open source ↗
  • Exploit-DBEDB-52310
    First seen May 29, 2025

    Windows File Explorer Windows 11 (23H2) - NTLM Hash Disclosure

    Open source ↗
  • GitHub PoCex-cal1bur/SMB_CVE-2025-24071
    First seen May 28, 2025

    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.

    Open source ↗
  • GitHub PoCLOOKY243/CVE-2025-24071-PoC
    First seen May 27, 2025

    CVE-2025-24071 Proof Of Concept

    Open source ↗
  • GitHub PoCMarcejr117/CVE-2025-24071_PoC
    First seen Mar 27, 2025

    A PoC of CVE-2025-24071 / CVE-2025-24054, A windows vulnerability that allow get NTMLv2 hashes

    Open source ↗
  • GitHub PoCThemeHackers/CVE-2025-24071
    First seen Mar 27, 2025

    Windows File Explorer Spoofing Vulnerability (CVE-2025-24071)

    Open source ↗
  • GitHub PoCctabango/CVE-2025-24071_PoCExtra
    First seen Mar 19, 2025

    Alternativa CVE-2025-24071_PoC

    Open source ↗
  • GitHub PoCFOLKS-iwd/CVE-2025-24071-msfvenom
    First seen Mar 18, 2025

    Metasploit module for CVE-2025-24071 - Windows NTLM Hash Leak via .library-ms

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-24071?
CVE-2025-24071 is a high vulnerability published on March 11, 2025. Exposure of sensitive information to an unauthorized actor in Windows File Explorer allows an unauthorized attacker to perform spoofing over a network.
When was CVE-2025-24071 disclosed?
CVE-2025-24071 was first published in the National Vulnerability Database on March 11, 2025, with the most recent update on July 3, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-24071 actively exploited?
CVE-2025-24071 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 23% probability of exploitation in the next 30 days, which ranks it in the top 2.3% of all scored CVEs.
What is the CVSS score of CVE-2025-24071?
CVE-2025-24071 has a CVSS v3 base score of 6.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 7.5.
How do I remediate CVE-2025-24071?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-24071, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-24071

Explore →

Is Your Infrastructure Affected by CVE-2025-24071?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs