CVE-2025-33073

Windows SMB Client Elevation of Privilege Vulnerability

HIGH

8.8

CVSS Score

Published: June 10, 2025 at 05:02 PM UTC

Updated: June 17, 2026 at 09:13 AM UTC

16 products affected across 1 vendorWindows Server 2016Windows Server 2019Windows Server 2012

Using Windows 10 Version 1809 by Microsoft?

Get instant alerts when new vulnerabilities affect Windows 10 Version 1809 - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

HIGH8.8

Exploitation

CISA KEV

Exploit prediction

EPSS 83%

SSVC

Active

Actively Exploited

CISA Known Exploited Vulnerabilities (KEV) Catalog

EPSS Score82.7%

EPSS (Exploit Prediction Scoring System) estimates a 82.7% chance this CVE is exploited in the wild within the next 30 days — higher than 100% of all CVEs. It complements CVSS: a high EPSS on a mid-severity CVE can still be urgent.

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.

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.

Ransomware Use

Unknown

Added to KEV

Oct 20, 2025

Remediation Due

Nov 10, 2025

350 days overdue

Notes

https://msrc.microsoft.com/update-guide/en-US/advisory/CVE-2025-33073

https://nvd.nist.gov/vuln/detail/CVE-2025-33073

Description

Improper access control in Windows SMB allows an authorized attacker to elevate privileges over a network.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Windows 10 1507 · Microsoft

95%

v < 10.0.10240.2103410.0.10240.0 ≤ v < 10.0.10240.2103410.0.10240.0

Affected range stops below 10.0.10240.21034, so it looks safe — our inference, not a vendor statement

Windows 10 1607 · Microsoft

95%

v < 10.0.14393.814810.0.14393.0 ≤ v < 10.0.14393.814810.0.14393.0

Affected range stops below 10.0.14393.8148, so it looks safe — our inference, not a vendor statement

Windows 10 1809 · Microsoft

95%

v < 10.0.17763.743410.0.17763.0 ≤ v < 10.0.17763.743410.0.17763.0

Affected range stops below 10.0.17763.7434, so it looks safe — our inference, not a vendor statement

Windows 10 21H2 · Microsoft

95%

v < 10.0.19044.596510.0.19044.0 ≤ v < 10.0.19044.596510.0.19044.0

Affected range stops below 10.0.19044.5965, so it looks safe — our inference, not a vendor statement

Windows 10 22H2 · Microsoft

95%

v < 10.0.19045.596510.0.19045.0 ≤ v < 10.0.19045.596510.0.19045.0

Affected range stops below 10.0.19045.5965, so it looks safe — our inference, not a vendor statement

Windows 11 22H2 · Microsoft

95%

v < 10.0.22621.547210.0.22621.0 ≤ v < 10.0.22621.547210.0.22621.0

Affected range stops below 10.0.22621.5472, so it looks safe — our inference, not a vendor statement

Windows 11 23H2 · Microsoft

95%

v < 10.0.22631.547210.0.22631.0 ≤ v < 10.0.22631.547210.0.22631.0

Affected range stops below 10.0.22631.5472, so it looks safe — our inference, not a vendor statement

Windows 11 24H2 · Microsoft

95%

v < 10.0.26100.427010.0.26100.0 ≤ v < 10.0.26100.434910.0.26100.0

Affected range stops below 10.0.26100.4270, so it looks safe — our inference, not a vendor statement

Affected range stops below 10.0.26100.4349, so it looks safe — our inference, not a vendor statement

Windows Server 2008 · Microsoft

95%

6.0.6003.0 ≤ v < 6.0.6003.233516.1.7601.0 ≤ v < 6.1.7601.277696.0.6003.0 6.1.7601.0 r2 sp1sp2

Affected range stops below 6.0.6003.23351, so it looks safe — our inference, not a vendor statement

Affected range stops below 6.1.7601.27769, so it looks safe — our inference, not a vendor statement

Windows Server 2012 · Microsoft

95%

6.2.9200.0 ≤ v < 6.2.9200.255226.3.9600.0 ≤ v < 6.3.9600.226206.2.9200.0 6.3.9600.0 r2

Affected range stops below 6.2.9200.25522, so it looks safe — our inference, not a vendor statement

Affected range stops below 6.3.9600.22620, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

References (4)

Vendor AdvisoryPatch

Source: [email protected]

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-33073

Third Party Advisory

Source: af854a3a-2127-422b-91ae-364da2661108

https://www.vicarius.io/vsociety/posts/cve-2025-33073-detection-script-improper-access-control-in-windows-smb-affects-microsoft-products

MitigationThird Party Advisory

Source: af854a3a-2127-422b-91ae-364da2661108

https://www.vicarius.io/vsociety/posts/cve-2025-33073-mitigation-script-improper-access-control-in-windows-smb-affects-microsoft-products

US Government Resource

Source: 134c704f-9b21-4f2e-91b3-4a467353bcc0

https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-33073

SSVC — Action Prioritization

SSVCActiveNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.8HIGHmicrosoft

Vector?

Quick Info

StatusANALYZED

CWE

CWE-284

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create account Sign in

Free plan, no card