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

> An authorized attacker can elevate privileges over the network via improper access control in the Windows SMB client.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C`)
- **Exploited in the wild:** Yes, since 20 Oct 2025 (CISA KEV)
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Jun 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-cfjg-2jr6-cgph, openSUSE-SU-2026:10837-1

## What is CVE-2025-33073?

CVE-2025-33073 is a high-severity vulnerability in Microsoft Windows 10 1507, published on 10 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2025-33073?

It affects 15 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `python-impacket` | openSUSE:Tumbleweed | All versions | 0.13.1-1.1 |

Products: Microsoft Windows 10 1507, Microsoft Windows 10 1607, Microsoft Windows 10 1809, Microsoft Windows 10 21h2, Microsoft Windows 10 22h2, Microsoft Windows 11 22h2, Microsoft Windows 11 23h2, Microsoft Windows 11 24h2, Microsoft Windows Server 2008, Microsoft Windows Server 2012, Microsoft Windows Server 2016, Microsoft Windows Server 2019, Microsoft Windows Server 2022, Microsoft Windows Server 2022 23h2, Microsoft Windows Server 2025.

## How do I fix CVE-2025-33073?

Apply the vendor's patch. US federal agencies must fix it by 10 Nov 2025.

## Is CVE-2025-33073 being exploited?

Yes. Attackers have exploited CVE-2025-33073 in the wild since at least 20 Oct 2025.

Public exploit code:

- PoC Exploit for the NTLM reflection SMB flaw. (github_poc): https://github.com/mverschu/CVE-2025-33073
- Universal exploitation tool for CVE-2025-33073 targeting Windows Domain Controllers with DNSAdmins privileges and WinRM enabled. (github_poc): https://github.com/uziii2208/CVE-2025-33073
- Proof-of-Concept (github_poc): https://github.com/SFRDevelopment/windows-smb-vulnerability-framework-cve-2025-33073
- cupntlm (github_poc): https://github.com/EgCupCake/cupntlm-Automated-Exploit-For-CVE-2025-33073-
- https://github.com/obscura-cert/CVE-2025-33073 (github_poc): https://github.com/obscura-cert/CVE-2025-33073
- Windows 11 SMB Client - Privilege Escalation & Remote Code Execution (RCE) (exploitdb)

## Other vulnerabilities in Microsoft Windows 10 1507

- [CVE-2017-8543](https://insights.sbomify.com/CVE-2017-8543/): Microsoft Windows Search Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2025-33053](https://insights.sbomify.com/CVE-2025-33053/): Microsoft Windows External Control of File Name or Path (high 8.8, exploited in the wild)
- [CVE-2024-49039](https://insights.sbomify.com/CVE-2024-49039/): Microsoft Windows Task Scheduler Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2024-43461](https://insights.sbomify.com/CVE-2024-43461/): Microsoft Windows MSHTML Platform Spoofing (high 8.8, exploited in the wild)
- [CVE-2024-30040](https://insights.sbomify.com/CVE-2024-30040/): Microsoft Windows MSHTML Platform Security Feature Bypass (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-33073 and fix it if it is affected.

What it is: CVE-2025-33073 is a high-severity vulnerability in Microsoft Windows 10 1507, published on 10 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2025-33073 in the wild since at least 20 Oct 2025.

Affected product: Microsoft Windows 10 1507. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-33073/ (Markdown: https://insights.sbomify.com/CVE-2025-33073/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-33073
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-33073
- OSV: https://osv.dev/vulnerability/CVE-2025-33073

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-33073/
Summaries are generated and may contain mistakes; the official description above is the record.