CVE-2025-33073
Improper access control in Windows SMB allows an authorized attacker to elevate privileges over a network.
do firstApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? No. The vulnerability is in the Windows SMB protocol, which is a network file sharing protocol, not HTTP. The malicious input is sent over SMB, and such traffic cannot be filtered by a web application firewall designed for HTTP.
Also consider: patch
Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2025-33073 being exploited?
Yes. CVE-2025-33073 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2025-33073?
CVE-2025-33073 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2025-33073?
Yes. A fix has been recorded for CVE-2025-33073. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2025-33073 affect?
CVE-2025-33073 affects microsoft:windows_10_1507, microsoft:windows_10_1607, microsoft:windows_10_1809, microsoft:windows_10_21h2, and 11 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affected>= 10.0.10240.0 and < 10.0.10240.21034
- affected>= 10.0.14393.0 and < 10.0.14393.8148
- affected>= 10.0.17763.0 and < 10.0.17763.7434
- affected>= 10.0.19044.0 and < 10.0.19044.5965
- affected>= 10.0.19045.0 and < 10.0.19045.5965
- affected>= 10.0.22621.0 and < 10.0.22621.5472
- affected>= 10.0.22631.0 and < 10.0.22631.5472
- affected>= 10.0.22631.0 and < 10.0.22631.5472
- affected>= 10.0.26100.0 and < 10.0.26100.4349
- affected>= 6.1.7601.0 and < 6.1.7601.27769
- affected>= 6.1.7601.0 and < 6.1.7601.27769
- affected>= 6.0.6003.0 and < 6.0.6003.23351
- affected>= 6.0.6003.0 and < 6.0.6003.23351
- affected>= 6.2.9200.0 and < 6.2.9200.25522
- affected>= 6.3.9600.0 and < 6.3.9600.22620
- affected>= 6.3.9600.0 and < 6.3.9600.22620
- affected>= 6.2.9200.0 and < 6.2.9200.25522
- affected>= 10.0.14393.0 and < 10.0.14393.8148
- affected>= 10.0.14393.0 and < 10.0.14393.8148
- affected>= 10.0.17763.0 and < 10.0.17763.7434
- affected>= 10.0.17763.0 and < 10.0.17763.7434
- affected>= 10.0.20348.0 and < 10.0.20348.3807
- affected>= 10.0.25398.0 and < 10.0.25398.1665
- affected>= 10.0.26100.0 and < 10.0.26100.4349
- affected>= 10.0.26100.0 and < 10.0.26100.4349
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
public exploits
Public exploit code: 1 on Exploit-DB · 11 GitHub proofs of concept
- Windows 11 SMB Client - Privilege Escalation & Remote Code Execution (RCE) · remote · 15 Jun 2025
- mverschu/CVE-2025-33073 · 720 ★
- uziii2208/CVE-2025-33073 · 68 ★
- SFRDevelopment/windows-smb-vulnerability-framework-cve-2025-33073 · 6 ★
- EgCupCake/cupntlm-Automated-Exploit-For-CVE-2025-33073- · 3 ★
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
cisa ssvc
- exploitation
- active
- automatable
- no
- technical impact
- total
Assessed by CISA 21 Oct 2025 (SSVC 2.0.3).
timeline
- 10 Jun 2025Published
- 13 Jun 2025First public exploit or proof of concept · 2 days later
- 20 Oct 2025Added to CISA KEV (exploited in the wild) · 129 days (about 4 months) later
- 21 Oct 2025CISA SSVC assessment: exploitation active · 1 day later
- 10 Nov 2025CISA remediation due date (US federal agencies) · 20 days later
- 26 Feb 2026CVE record last updated · 109 days (about 4 months) later
- 2 Nov 2026Analysed by vulneraibility.com · 249 days (about 8 months) later
- Patchmsrc.microsoft.com /update-guide/vulnerability/CVE-2025-33073
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-33073
- Linkvicarius.io /vsociety/posts/cve-2025-33073-detection-script-improper-access-control-in-windo
- Linkvicarius.io /vsociety/posts/cve-2025-33073-mitigation-script-improper-access-control-in-wind
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Exploit-DB: published exploits
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.