CVE-2025-33073 — Microsoft Windows SMB Client Improper Access Control Vulnerability

CVE-2025-33073

Microsoft Windows — SMB Client Coercion Attack; Credential Relay / Privilege Escalation via Malicious Script

What is Windows SMB Client Authentication Coercion?

Server Message Block (SMB) is the Windows file-sharing and authentication protocol. Windows systems automatically authenticate to SMB servers they connect to, presenting their NTLM hash or Kerberos ticket. Attackers can exploit this behavior to coerce a victim machine into initiating an SMB connection to an attacker-controlled server — capturing the NTLM hash for relay attacks or offline cracking. This class of attack (SMB coercion/relay) has been used for decades and remains relevant because Windows automatically handles SMB authentication without user confirmation.

Overview

CVE-2025-33073 is an improper access control (CWE-284) vulnerability in the Windows SMB Client that allows an attacker with low-level network access to coerce a victim machine into connecting to an attacker-controlled SMB server. The coercion is triggered by executing a specially crafted malicious script — once a low-privilege attacker can run code on the victim's machine or interact with it via network, they can trigger the SMB authentication to relay or capture the victim's credentials, enabling privilege escalation.

Affected Versions

Product Vulnerable Fixed
Windows 10 / 11 (all supported versions) Before June 2025 cumulative update June 2025 cumulative update
Windows Server 2019–2025 Before June 2025 cumulative update June 2025 cumulative update

Technical Details

The vulnerability is an improper access control (CWE-284) in the Windows SMB Client that allows an attacker-controlled script to trigger SMB authentication against an attacker-specified server. The "script" referenced can be a PowerShell script, batch file, or Office macro that a low-privilege user executes or is tricked into executing.

When the victim machine connects to the attacker's SMB server, it automatically authenticates using NTLM (or Kerberos if applicable). The attacker captures the NTLM hash and either:

  • Relays it in real-time to another service (SMB relay, LDAP relay) to authenticate as the victim user
  • Cracks it offline to recover the plaintext password

SMB relay is particularly effective if SMB signing is not enforced on target servers, and NTLM hash relay to LDAP can enable domain account enumeration or modification.

Discovery

Patched in June 2025 Patch Tuesday; active exploitation confirmed per CISA KEV addition in October 2025.

Exploitation Context

CISA added this to the KEV catalog on October 20, 2025 — four months after the patch, confirming ongoing exploitation in the wild against unpatched systems. SMB coercion techniques (Responder, PetitPotam, PrinterBug, etc.) are standard tools in red team and ransomware pre-deployment lateral movement phases. No specific threat actor was named.

Remediation

  1. Apply the June 2025 cumulative update for your Windows version. The CISA deadline was November 10, 2025.
  2. Enforce SMB signing on all domain controllers and member servers — this prevents NTLM relay even if coercion is successful.
  3. Block outbound SMB (TCP 445) to the internet at the perimeter firewall — victim machines should not be able to connect to external SMB servers.
  4. Disable NTLM authentication where Kerberos is available, or restrict NTLM using Group Policy (Network Security: Restrict NTLM).
  5. Monitor for NTLM authentication events from unexpected source machines to internal servers (Event ID 4624 Type 3 NTLM logons from unusual sources).

Key Details

PropertyValue
CVE ID CVE-2025-33073
Vendor / Product Microsoft — Windows
NVD Published2025-06-10
NVD Last Modified2025-10-27
CVSS 3.1 Score8.8
CVSS 3.1 VectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
SeverityHIGH
CWE CWE-284 find similar ↗
CISA KEV Added2025-10-20
CISA KEV Deadline2025-11-10
Known Ransomware Use No

CVSS 3.1 Breakdown

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Required Action

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

Timeline

DateEvent
2025-06-10Patched in June 2025 Patch Tuesday
2025-10-20Added to CISA Known Exploited Vulnerabilities catalog
2025-11-10CISA BOD 22-01 remediation deadline