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

Published Jun 10, 2025
·
Updated

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

Other sources

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.

CISA

Windows SMB Client Elevation of Privilege Vulnerability

Microsoft

Affected Software

96 affected componentsFixes available
Microsoft Windows Server 2008
Microsoft Windows Server 2008 R2
Microsoft Windows Server 2016
Microsoft Windows Server 2008 R2
Microsoft Windows 10=1607
Microsoft Windows Server 2008
Microsoft Windows Server 2016
Microsoft Windows Server 2008
Microsoft Windows 10=1607
Microsoft Windows Server 2008
Microsoft Windows Server 2022
Microsoft Windows Server 2019
Microsoft Windows Server 2012
Microsoft Windows 10=22H2
Microsoft Windows 10
Microsoft Windows Server 2012
Microsoft Windows 10=22H2
Microsoft Windows 11=24H2
Microsoft Windows 10=1809
Microsoft Windows 10=22H2
Microsoft Windows Server 2012 R2
Microsoft Windows 10=21H2
Microsoft Windows 10=1809
Microsoft Windows 11=24H2
Microsoft Windows 10=21H2
Microsoft Windows 11=23H2
Microsoft Windows 10=21H2
Microsoft Windows 11=22H2
Microsoft Windows Server 2025
Microsoft Windows 11=22H2
Microsoft Windows Server 2019
Microsoft Windows Server 2022, 23H2 Edition
Microsoft Windows 10
Microsoft Windows Server 2025
Microsoft Windows 11=23H2
Microsoft Windows Server 2022
Microsoft Windows Server 2012 R2
Microsoft Windows
Microsoft Windows 10 1507<10.0.10240.21034
Microsoft Windows 10 1507<10.0.10240.21034
Microsoft Windows 10 1607<10.0.14393.8148
Microsoft Windows 10 1607<10.0.14393.8148
Microsoft Windows 10 1809<10.0.17763.7434
Microsoft Windows 10 1809<10.0.17763.7434
Microsoft Windows 10 21h2<10.0.19044.5965
Microsoft Windows 10 22h2<10.0.19045.5965
Microsoft Windows 11 22h2<10.0.22621.5472
Microsoft Windows 11 23h2<10.0.22631.5472
Microsoft Windows 11 24h2<10.0.26100.4270
Microsoft Windows Server 2008=sp2
Microsoft Windows Server 2008=sp2
Microsoft Windows Server 2008=r2-sp1
Microsoft Windows Server 2012
Microsoft Windows Server 2012=r2
Microsoft Windows Server 2016<10.0.14393.8148
Microsoft Windows Server 2019<10.0.17763.7434
Microsoft Windows Server 2022<10.0.20348.3745
Microsoft Windows Server 2022 23h2<10.0.25398.1665
Microsoft Windows Server 2025<10.0.26100.4270
Microsoft Windows 11=22H2
10.0.22621.5472
Microsoft Windows 11=22H2
10.0.22621.5472
Microsoft Windows 10=21H2
10.0.19044.5965
Microsoft Windows 10=21H2
10.0.19044.5965
Microsoft Windows Server 2022<10.0.20348.3807, <10.0.20348.3745
10.0.20348.380710.0.20348.3745
Microsoft Windows 10=21H2
10.0.19044.5965
Microsoft Windows Server 2012 R2<6.3.9600.22620
6.3.9600.22620
Microsoft Windows Server 2012<6.2.9200.25522
6.2.9200.25522
Microsoft Windows Server 2012 R2<6.3.9600.22620
6.3.9600.22620
Microsoft Windows Server 2008 R2<6.1.7601.27769
6.1.7601.27769
Microsoft Windows Server 2012<6.2.9200.25522
6.2.9200.25522
Microsoft Windows Server 2008 R2<6.1.7601.27769
6.1.7601.27769
Microsoft Windows Server 2016<10.0.14393.8148
10.0.14393.8148
Microsoft Windows Server 2008<6.0.6003.23351
6.0.6003.23351
Microsoft Windows Server 2016<10.0.14393.8148
10.0.14393.8148
Microsoft Windows Server 2008<6.0.6003.23351
6.0.6003.23351
Microsoft Windows 10=1607
10.0.14393.8148
Microsoft Windows 10<10.0.10240.21034
10.0.10240.21034
Microsoft Windows Server 2008<6.0.6003.23351
6.0.6003.23351
Microsoft Windows Server 2008<6.0.6003.23351
6.0.6003.23351
Microsoft Windows 10=1607
10.0.14393.8148
Microsoft Windows Server 2025<10.0.26100.4349, <10.0.26100.4270
10.0.26100.434910.0.26100.4270
Microsoft Windows 10<10.0.10240.21034
10.0.10240.21034
Microsoft Windows 11=24H2
10.0.26100.434910.0.26100.4270
Microsoft Windows 11=24H2
10.0.26100.434910.0.26100.4270
Microsoft Windows 11=23H2
10.0.22631.5472
Microsoft Windows Server 2025<10.0.26100.4349, <10.0.26100.4270
10.0.26100.434910.0.26100.4270
Microsoft Windows Server 2022, 23H2 Edition<10.0.25398.1665
10.0.25398.1665
Microsoft Windows 11=23H2
10.0.22631.5472
Microsoft Windows 10=22H2
10.0.19045.5965
Microsoft Windows 10=22H2
10.0.19045.5965
Microsoft Windows Server 2022<10.0.20348.3807, <10.0.20348.3745
10.0.20348.380710.0.20348.3745
Microsoft Windows 10=1809
10.0.17763.7434
Microsoft Windows 10=1809
10.0.17763.7434
Microsoft Windows Server 2019<10.0.17763.7434
10.0.17763.7434
Microsoft Windows Server 2019<10.0.17763.7434
10.0.17763.7434
Microsoft Windows 10=22H2
10.0.19045.5965

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.22621.5472Patch KB5060999
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.19044.5965Patch KB5060533
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.20348.3807Fixed in 10.0.20348.3745Patch KB5060525
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.3.9600.22620Patch KB5061018
  5. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.2.9200.25522Patch KB5061059
  6. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.1.7601.27769Patch KB5061036
  7. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.14393.8148Patch KB5061010
  8. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.0.6003.23351Patch KB5061072
  9. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.10240.21034Patch KB5060998
  10. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.26100.4349Fixed in 10.0.26100.4270Patch KB5060841
  11. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.22631.5472Patch KB5060999
  12. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.25398.1665Patch KB5060118
  13. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.19045.5965Patch KB5060533
  14. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.17763.7434Patch KB5060531

Event History

Jun 10, 2025
CVE Published
via Microsoft·07:00 AM
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
Description
CVE Published
via MITRE·05:02 PM
Data Sourced
via MITRE·05:02 PM
DescriptionSeverity
Data Sourced
via NVD·05:23 PM
DescriptionSeverityWeaknessAffected Software
News Published
via Dark Reading·09:56 PM
News Published
via The Register·11:38 PM
News Published
via The Register·11:44 PM
Jun 15, 2025
Exploit Published
12:00 AM
Oct 20, 2025
Known Exploited
via CISA·12:00 AM
Data Sourced
via CISA·12:00 AM
RemedyDescriptionAffected Software
News Published
via BleepingComputer·05:18 PM
News Published
via BleepingComputer·05:20 PM
Oct 21, 2025
News Published
via The Register·10:27 AM
May 12, 2026
News Published
via Dark Reading·10:19 AM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-33073?

CVE-2025-33073 has a high severity rating due to its potential for privilege escalation over the network.

2

How do I fix CVE-2025-33073?

To fix CVE-2025-33073, apply the pertinent security patches provided by Microsoft for the affected Windows versions.

3

What systems are affected by CVE-2025-33073?

CVE-2025-33073 affects multiple versions of Windows including Windows 10, Windows 11, and various Windows Server editions.

4

What is the impact of CVE-2025-33073?

The impact of CVE-2025-33073 allows an attacker with authorized access to elevate their privileges on affected systems.

5

Is there a workaround for CVE-2025-33073?

There are no recommended workarounds for CVE-2025-33073; patching is the advised method of mitigation.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203