Skip to content
vulnerability

CVE-2025-33053

8.8
High
KEV · Exploited in wildEPSS 87%Patch available

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

exploited
Yes, in CISA KEV since 10 Jun 2025fix by 1 Jul 2025 (CISA deadline for US federal agencies)public exploit code
fix
Patch available see the advisory in the references
likelihood
EPSS 87.0%
Published 10 Jun 2025Analysed here 2 Nov 2026CVSS scored by the publisher (CNA)

do firstApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

triage
surface unknownruntimeWAF can block: partlyAV · networkCWE-73· Common Weakness

Can a WAF block it? Partly. The bug can be reached over the network, so generic WAF rules may stop some attacks. Its weakness type is unknown, so we cannot be more precise.

Also consider: patch

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.

cvss vector
attack vectornetworkattack complexitylowprivileges requirednoneuser interactionrequiredscopeunchangedconfidentialityhighintegrityhighavailabilityhigh
CVSS 3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
common questions

Is CVE-2025-33053 being exploited?

Yes. CVE-2025-33053 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2025-33053?

CVE-2025-33053 is rated High with a CVSS score of 8.8. 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-33053?

Yes. A fix has been recorded for CVE-2025-33053. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2025-33053 affect?

CVE-2025-33053 affects microsoft:windows_10_1507, microsoft:windows_10_1607, microsoft:windows_10_1809, microsoft:windows_10_21h2, and 11 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.

executive summary
technical analysis
affected
microsoft:windows_10_1507microsoft:windows_10_1607microsoft:windows_10_1809microsoft:windows_10_21h2microsoft:windows_10_22h2microsoft:windows_11_22h2microsoft:windows_11_23h2microsoft:windows_11_24h2microsoft:windows_server_2008microsoft:windows_server_2012microsoft:windows_server_2016microsoft:windows_server_2019microsoft:windows_server_2022microsoft:windows_server_2022_23h2microsoft:windows_server_2025
affected versions
Microsoft Windows 10 Version 1507
  • affected>= 10.0.10240.0 and < 10.0.10240.21034
Microsoft Windows 10 Version 1607
  • affected>= 10.0.14393.0 and < 10.0.14393.8148
Microsoft Windows 10 Version 1809
  • affected>= 10.0.17763.0 and < 10.0.17763.7434
Microsoft Windows 10 Version 21H2
  • affected>= 10.0.19044.0 and < 10.0.19044.5965
Microsoft Windows 10 Version 22H2
  • affected>= 10.0.19045.0 and < 10.0.19045.5965
Microsoft Windows 11 version 22H2
  • affected>= 10.0.22621.0 and < 10.0.22621.5472
Microsoft Windows 11 version 22H3
  • affected>= 10.0.22631.0 and < 10.0.22631.5472
Microsoft Windows 11 Version 23H2
  • affected>= 10.0.22631.0 and < 10.0.22631.5472
Microsoft Windows 11 Version 24H2
  • affected>= 10.0.26100.0 and < 10.0.26100.4349
Microsoft Windows Server 2008 R2 Service Pack 1
  • affected>= 6.1.7601.0 and < 6.1.7601.27769
Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)
  • affected>= 6.1.7601.0 and < 6.1.7601.27769
Microsoft Windows Server 2008 Service Pack 2
  • affected>= 6.0.6003.0 and < 6.0.6003.23351
Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)
  • affected>= 6.0.6003.0 and < 6.0.6003.23351
Microsoft Windows Server 2012
  • affected>= 6.2.9200.0 and < 6.2.9200.25522
Microsoft Windows Server 2012 R2
  • affected>= 6.3.9600.0 and < 6.3.9600.22620
Microsoft Windows Server 2012 R2 (Server Core installation)
  • affected>= 6.3.9600.0 and < 6.3.9600.22620
Microsoft Windows Server 2012 (Server Core installation)
  • affected>= 6.2.9200.0 and < 6.2.9200.25522
Microsoft Windows Server 2016
  • affected>= 10.0.14393.0 and < 10.0.14393.8148
Microsoft Windows Server 2016 (Server Core installation)
  • affected>= 10.0.14393.0 and < 10.0.14393.8148
Microsoft Windows Server 2019
  • affected>= 10.0.17763.0 and < 10.0.17763.7434
Microsoft Windows Server 2019 (Server Core installation)
  • affected>= 10.0.17763.0 and < 10.0.17763.7434
Microsoft Windows Server 2022
  • affected>= 10.0.20348.0 and < 10.0.20348.3807
Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)
  • affected>= 10.0.25398.0 and < 10.0.25398.1665
Microsoft Windows Server 2025
  • affected>= 10.0.26100.0 and < 10.0.26100.4349
Microsoft Windows Server 2025 (Server Core installation)
  • affected>= 10.0.26100.0 and < 10.0.26100.4349

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.

public exploits

Public exploit code: 1 Metasploit module · 5 GitHub proofs of concept

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.

cisa ssvc

exploitation
active
automatable
no
technical impact
total

Assessed by CISA 20 Aug 2025 (SSVC 2.0.3).

timeline

  1. 10 Jun 2025Added to CISA KEV (exploited in the wild)
  2. 10 Jun 2025Published · 1 day later
  3. 12 Jun 2025First public exploit or proof of concept · 1 day later
  4. 1 Jul 2025CISA remediation due date (US federal agencies) · 19 days later
  5. 20 Aug 2025CISA SSVC assessment: exploitation active · 50 days later
  6. 26 Feb 2026CVE record last updated · 191 days (about 6 months) later
  7. 2 Nov 2026Analysed by vulneraibility.com · 249 days (about 8 months) later
how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
9 references in the CVE record: 1 patch, 8 links
  • Patchmsrc.microsoft.com /update-guide/vulnerability/CVE-2025-33053
  • Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-33053
  • Linkresearch.checkpoint.com /2025/stealth-falcon-zero-day/
  • Linkdarkreading.com /vulnerabilities-threats/stealth-falcon-apt-exploits-microsoft-rce-zero-day-mide
  • Linktherecord.media /microsoft-cisa-zero-day-turkish-defense-org
  • Linkbleepingcomputer.com /news/security/stealth-falcon-hackers-exploited-windows-webdav-zero-day-to-drop-
  • Linktheregister.com /2025/06/10/microsoft_patch_tuesday_june/
  • Linkvicarius.io /vsociety/posts/cve-2025-33053-mitigation-script-remote-code-execution-vulnerabi
Show 1 more
  • Linkvicarius.io /vsociety/posts/cve-2025-33053-detection-script-remote-code-execution-vulnerabil

sources

get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved