Skip to content
Server Security Center
KEVhigh8.8

CVE-2025-33053: Microsoft Windows External Control of File Name or Path

Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2025-06-10.

CVSS v3.1 (CVE record)
8.8
high
EPSS (exploit probability, 30 days)
87%
higher than 99.7% of all CVEs
Added to CISA KEV
2025-06-10
US federal due date 2025-07-01
Automatable (CISA SSVC)
no
technical impact: total

CVE-2025-33053 explained

CVE-2025-33053 is an external control of file name or path weakness in the handling of Internet Shortcut Files in Microsoft Windows. An unauthorized attacker can use it to execute code over a network. CISA lists it as known exploited, so affected Windows desktops and servers should be patched promptly.

Impact

An attacker without privileges can run code on a target system over the network. The user must take some action, such as opening a crafted Internet Shortcut File. Successful exploitation fully compromises confidentiality, integrity and availability. CISA rates the technical impact as total but considers it not automatable, so attacks need user involvement rather than mass scanning. Attackers are known to exploit this vulnerability. Ransomware use is listed as unknown.

Who is affected

The record lists Windows 10 versions 1507, 1607, 1809, 21H2 and 22H2. It also lists Windows 11 versions 22H2, 22H3, 23H2 and 24H2, and Windows Server 2008 SP2 and 2008 R2 SP1, including Server Core. Fixed builds include 10.0.10240.21034, 10.0.14393.8148, 10.0.17763.7434, 10.0.19044.5965, 10.0.19045.5965, 10.0.22621.5472, 10.0.22631.5472, 10.0.26100.4349, 6.1.7601.27769 and 6.0.6003.23351. The page lists 13 further products.

Written with AI from the data on this page and checked against it automatically.

Official description

External control of file name or path in Internet Shortcut Files allows an unauthorized attacker to execute code over a network.

CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • Microsoft Windows 10 Version 150732-bit, x64
    Affected
    • < 10.0.10240.21034
    Fixed in
    • 10.0.10240.21034
  • Microsoft Windows 10 Version 160732-bit, x64
    Affected
    • < 10.0.14393.8148
    Fixed in
    • 10.0.14393.8148
  • Microsoft Windows 10 Version 180932-bit, x64
    Affected
    • < 10.0.17763.7434
    Fixed in
    • 10.0.17763.7434
  • Microsoft Windows 10 Version 21H232-bit, ARM64, x64
    Affected
    • < 10.0.19044.5965
    Fixed in
    • 10.0.19044.5965
  • Microsoft Windows 10 Version 22H232-bit, ARM64, x64
    Affected
    • < 10.0.19045.5965
    Fixed in
    • 10.0.19045.5965
  • Microsoft Windows 11 version 22H2ARM64, x64
    Affected
    • < 10.0.22621.5472
    Fixed in
    • 10.0.22621.5472
  • Microsoft Windows 11 version 22H3ARM64
    Affected
    • < 10.0.22631.5472
    Fixed in
    • 10.0.22631.5472
  • Microsoft Windows 11 Version 23H2x64
    Affected
    • < 10.0.22631.5472
    Fixed in
    • 10.0.22631.5472
  • Microsoft Windows 11 Version 24H2ARM64, x64
    Affected
    • < 10.0.26100.4349
    Fixed in
    • 10.0.26100.4349
  • Microsoft Windows Server 2008 R2 Service Pack 1x64
    Affected
    • < 6.1.7601.27769
    Fixed in
    • 6.1.7601.27769
Show 15 more products
  • Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)x64
    Affected
    • < 6.1.7601.27769
    Fixed in
    • 6.1.7601.27769
  • Microsoft Windows Server 2008 Service Pack 232-bit, x64
    Affected
    • < 6.0.6003.23351
    Fixed in
    • 6.0.6003.23351
  • Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)32-bit, x64
    Affected
    • < 6.0.6003.23351
    Fixed in
    • 6.0.6003.23351
  • Microsoft Windows Server 2012x64
    Affected
    • < 6.2.9200.25522
    Fixed in
    • 6.2.9200.25522
  • Microsoft Windows Server 2012 (Server Core installation)x64
    Affected
    • < 6.2.9200.25522
    Fixed in
    • 6.2.9200.25522
  • Microsoft Windows Server 2012 R2x64
    Affected
    • < 6.3.9600.22620
    Fixed in
    • 6.3.9600.22620
  • Microsoft Windows Server 2012 R2 (Server Core installation)x64
    Affected
    • < 6.3.9600.22620
    Fixed in
    • 6.3.9600.22620
  • Microsoft Windows Server 2016x64
    Affected
    • < 10.0.14393.8148
    Fixed in
    • 10.0.14393.8148
  • Microsoft Windows Server 2016 (Server Core installation)x64
    Affected
    • < 10.0.14393.8148
    Fixed in
    • 10.0.14393.8148
  • Microsoft Windows Server 2019x64
    Affected
    • < 10.0.17763.7434
    Fixed in
    • 10.0.17763.7434
  • Microsoft Windows Server 2019 (Server Core installation)x64
    Affected
    • < 10.0.17763.7434
    Fixed in
    • 10.0.17763.7434
  • Microsoft Windows Server 2022x64
    Affected
    • < 10.0.20348.3807
    Fixed in
    • 10.0.20348.3807
  • Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)x64
    Affected
    • < 10.0.25398.1665
    Fixed in
    • 10.0.25398.1665
  • Microsoft Windows Server 2025x64
    Affected
    • < 10.0.26100.4349
    Fixed in
    • 10.0.26100.4349
  • Microsoft Windows Server 2025 (Server Core installation)x64
    Affected
    • < 10.0.26100.4349
    Fixed in
    • 10.0.26100.4349

How to fix it

  • Update to the fixed version for your product:
    • Microsoft Windows 10 Version 1507: 10.0.10240.21034
    • Microsoft Windows 10 Version 1607: 10.0.14393.8148
    • Microsoft Windows 10 Version 1809: 10.0.17763.7434
    • Microsoft Windows 10 Version 21H2: 10.0.19044.5965
    • Microsoft Windows 10 Version 22H2: 10.0.19045.5965
    • Microsoft Windows 11 version 22H2: 10.0.22621.5472
    Fixed versions for 19 more products are in the table above.
  • Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2025-33053
  • CISA's deadline for US federal agencies: 2025-07-01 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Install the Microsoft security update that brings each affected system to the fixed build listed for its Windows version.
  2. Prioritize patching, as CISA lists this vulnerability as known exploited. The US federal due date was 2025-07-01.
  3. Follow the Microsoft advisory for any further mitigations, and check the additional products listed on this page.
  4. Warn users not to open Internet Shortcut Files from untrusted sources, such as email attachments or downloads.
  5. Review systems for signs of compromise, especially unpatched hosts where users opened suspicious shortcut files.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

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

Questions about CVE-2025-33053

Is CVE-2025-33053 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2025-06-10. Whether it has been used in ransomware campaigns is listed as unknown.
Does exploitation require user interaction?
Yes. The CVSS vector requires user interaction, and CISA rates the vulnerability as not automatable. No privileges are needed, and the attack can come over a network.
Which Windows Server versions are affected?
The CVE record lists Windows Server 2008 Service Pack 2, fixed in 6.0.6003.23351. It also lists Windows Server 2008 R2 Service Pack 1, including Server Core installations, fixed in 6.1.7601.27769. The page lists further products beyond these.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.