CVE-2025-33073 Microsoft Windows SMB Client Improper Access Control Vulnerability
Microsoft Windows SMB Client contains an improper access control vulnerability that could allow for privilege escalation. An attacker could execute a specially crafted malicious script to coerce the victim machine to connect back to the attack system using SMB and authenticate.
From the CISA KEV catalogue version 2026.11.06, with Cybergen analysis. Updated 6 Nov 2026.
Should You Worry?
- CISA confirmed exploitation in the wild and added it to the Known Exploited Vulnerabilities catalogue on 20 Oct 2025.
- Rated High severity (CVSS 8.8, scored by Vendor).
- Named in Cybergen threat actor reporting: The Gentlemen.
- It has been in the catalogue for 382 days. Systems still unpatched now have almost certainly been scanned for it.
What It Is
Improper access control in Windows SMB allows an authorized attacker to elevate privileges over a network.
Affected Versions
| Product | Versions |
|---|---|
| Microsoft Windows 10 Version 1507 | 10.0.10240.0 to before 10.0.10240.21034 |
| Microsoft Windows 10 Version 1607 | 10.0.14393.0 to before 10.0.14393.8148 |
| Microsoft Windows 10 Version 1809 | 10.0.17763.0 to before 10.0.17763.7434 |
| Microsoft Windows 10 Version 21H2 | 10.0.19044.0 to before 10.0.19044.5965 |
| Microsoft Windows 10 Version 22H2 | 10.0.19045.0 to before 10.0.19045.5965 |
| Microsoft Windows 11 version 22H2 | 10.0.22621.0 to before 10.0.22621.5472 |
From the public CVE record, as supplied by the vendor. Always confirm against the vendor advisory.
What To Do Now
- 1
Find it
Search your asset inventory and external attack surface for Microsoft Windows. Include cloud images, appliances and anything a supplier runs for you.
Attack Surface Management - 2
Fix it
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Vulnerability Management - 3
Hunt for compromise
If an affected system was reachable before you patched, assume it may have been hit. Check logs, new accounts, web shells and outbound connections from the date of exposure.
Incident Response - 4
Prove it is fixed
Rescan or test the system after patching. Upgrades that fail silently and forgotten secondary instances are common.
Penetration Testing
The Compliance Clock
General guidance, not legal advice. Your obligations depend on your sector, scope and jurisdiction.
Not Sure If You Are Exposed?
Our attack surface and vulnerability teams can check your internet-facing estate for CVE-2025-33073 and every other exploited flaw on the list.