CVE-2025-33073
Windows SMB Client Elevation of Privilege Vulnerability
Exploited in the wild. In CISA KEV since 2025‑10‑20. A vendor fix is available.
What to do
The vendor has published a fix. Version details are below where the sources state them.
Steps
Written by AI from the record- Check whether any of your devices run Microsoft Windows SMB Client on the affected versions (Windows Server 2008/2012/2012 R2/2008 R2/2016/2019/2022/2025 and Windows 10/11).
- For each affected device, confirm the installed Windows update level matches or exceeds the fixed version for your edition (see step 3).
- Apply the vendor fixes: upgrade Windows 10/Server 2016/Server 2019 to at least 10.0.19044.5965 / 10.0.19045.5965 / 10.0.17763.7434 / 10.0.14393.8148 as applicable; upgrade Windows 11 to at least 10.0.22621.5472 / 10.0.22631.5472 / 10.0.26100.4270 as applicable; upgrade Windows Server 2022 to at least 10.0.20348.3745 / 10.0.25398.1665 as applicable.
- If a system can’t be patched right away, use the vendor mitigation/workaround guidance from Microsoft Update Guide for CVE-2025-33073 and restrict or isolate SMB network access until patching is completed.
What it is
From the CVE record
Improper access control in Windows SMB allows an authorized attacker to elevate privileges over a network.
In plain language
Written by AI from the recordCVE-2025-33073 is a Windows SMB issue where an attacker with network access can gain higher privileges; most small businesses should treat it as urgent and patch soon.
CVE-2025-33073 is a Windows SMB Client elevation of privilege issue (CWE-284) where an authorized attacker can exploit improper access control to elevate privileges over the network; it is listed in CISA KEV with a remediation due date of 2025-11-10.
If you're affected
- Complete takeover of affected systems
- Account and admin privilege escalation
- Malicious activity without clear access
- Disruption from unauthorized control
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Listed as exploited in the wild since 2025-10-20.
US federal agencies must remediate by 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.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
83% chance of exploitation activity in the next 30 days, which ranks it in the 99th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
9 events over 380 days, from the signal feeds we watch.
- OpenVAS check added
- EPSS band changemoderate → high
- EPSS band changehigh → moderate
- Patch availableworkaround available, record updated
- Added to CISA KEV
- Publishedweakness classified
Affected products
- Windows Server 2008 Service Pack 2 (Server Core Installation)Operating Systems / windows
- Windows Server 2012 (Server Core installation)Operating Systems / windows
- Windows Server 2012 R2 (Server Core installation)Operating Systems / windows
- Windows Server 2008 R2 Service Pack 1 (Server Core installation)Operating Systems / windows
- Windows 10 Version 1507Operating Systems / windows
- Windows Server 2016 (Server Core installation)Operating Systems / windows
- Windows Server 2019 (Server Core installation)Operating Systems / windows
- Windows Server 2022 (Server Core installation)Operating Systems / windows
And 57 more affected products. See all after sign-in
Technical detail
CVSS 3.1 vector
Open in the CVSS calculatorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Scored 8.8 by NVD.
How it is reached
- Attack Vector NetworkExploitable remotely over the network without any special conditions
- Attack Complexity LowNo special conditions — the attack can be reliably reproduced
- Privileges Required LowRequires basic user-level privileges
- User Interaction NoneNo user interaction needed — fully automated exploitation
Scope
- Scope UnchangedImpact is limited to the vulnerable component itself
Impact if exploited
- Confidentiality HighTotal information disclosure — all data in the component is compromised
- Integrity HighTotal loss of integrity — attacker can modify any data in the component
- Availability HighTotal denial of service — the component is completely unavailable
Weaknesses
Sources
References in the record
- msrc.microsoft.com/update-guide/vulnerability/CVE-2025-33073&
- helpnetsecurity.com/2025/06/11/microsoft-fixes-zero-day-exploited-for-cyber-espionage-cve-2025-33053/&
- synacktiv.com/publications/ntlm-reflection-is-dead-long-live-ntlm-reflection-an-in-depth-analysis-of-cve-2025&
And 6 more references. See all after sign-in
In the news
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next exploited one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Microsoft Corp, not every advisory. This one: actively exploited.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI