dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 10 Nov 2025.
Windows 10 1507Operating system · Microsoft

CVE-2025-33073

HIGH · 8.8 CVSS v3.1 Published 2025-06-10
Fix available
A fix is available. Upgrade to 10.0.10240.21034 / 10.0.14393.8148 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

CVE-2025-33073 is an improper access control vulnerability in Windows SMB (Server Message Block) that allows an authorized attacker to elevate privileges over a network. The flaw appears to involve a bypass or misconfiguration in SMB's access control mechanisms, enabling authenticated users to gain higher-level permissions than intended.

MitigationApply Microsoft security patches for CVE-2025-33073 to all affected Windows systems. Until patched, consider restricting SMB access via firewall rules, disabling SMB version 1 if unnecessary, and enforcing SMB signing to reduce attack surface.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Windows 10 1507Operating system
Affected:< 10.0.10240.21034
Windows 10 1607Operating system
Affected:< 10.0.14393.8148
Windows 10 1809Operating system
Affected:< 10.0.17763.7434
Windows 10 21h2Operating system
Affected:< 10.0.19044.5965
Windows 10 22h2Operating system
Affected:< 10.0.19045.5965
Windows 11 22h2Operating system
Affected:< 10.0.22621.5472
Windows 11 23h2Operating system
Affected:< 10.0.22631.5472
Windows 11 24h2Operating system
Affected:< 10.0.26100.4270

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Windows build version
    Open Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to retrieve the installed Windows build number
    Affected if The build number is lower than any of the following: 10.0.10240.21034 (Windows 10 1507), 10.0.14393.8148 (Windows 10 1607), 10.0.17763.7434 (Windows 10 1809), 10.0.19044.5965 (Windows 10 21h2/22h2), 10.0.22621.5472 (Windows 11 22h2), 10.0.22631.5472 (Windows 11 23h2), 10.0.26100.4270 (Windows 11 24h
  2. Verify SMB service status
    Open PowerShell and run 'Get-Service -Name "LanmanServer" | Select-Object Name, Status' or 'sc query lanmanserver' to check if the SMB service is running
    Affected if The SMB service (LanmanServer) is running on a Windows version with a build number below the fixed versions listed above
  3. Enumerate SMB shares and their permissions
    Run 'Get-SmbShare -Special $false' in PowerShell, then inspect each share's access control with 'Get-SmbShareAccess -Name "<ShareName>"' to review who has access
    Affected if SMB shares exist and the system is running an affected Windows build, particularly if shares grant broad access to authenticated users
  4. Check for SMBv1 usage
    Run 'Get-WindowsOptionalFeature -Online -FeatureName SMB1Protocol' in PowerShell to determine if SMBv1 is enabled, which may increase exposure
    Affected if SMBv1 is enabled and the Windows build is below the fixed version numbers

A system is affected if it runs any Windows 10 or 11 version with a build number lower than the fixed builds AND has SMB (LanmanServer) service enabled and accessible over the network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.0.10240.21034 / 10.0.14393.8148 / 10.0.17763.7434 or later
Fixed in 10.0.10240.2103410.0.14393.814810.0.17763.7434
Interim mitigation

Apply Microsoft security patches for CVE-2025-33073 to all affected Windows systems. Until patched, consider restricting SMB access via firewall rules, disabling SMB version 1 if unnecessary, and enforcing SMB signing to reduce attack surface.

Recommended fix High confidence

Apply the latest Windows Security Cumulative Update for your specific Windows version to reach the minimum fixed build number listed in the affected versions

  1. Open Windows Settings and navigate to Update & Security > Windows Update
  2. Click 'Check for updates' to download and install the latest cumulative security updates
  3. Verify the installed build number matches or exceeds the fixed version for your Windows edition: Windows 10 1507 requires build 10.0.10240.21034, Windows 10 1607 requires build 10.0.14393.8148, Windows 10 1809 requires build 10.0.17763.7434, Windows 10 21h2 requires build 10.0.19044.5965, Windows 10 22h2 requires build 10.0.19045.5965, Windows 11 22h2 requires build 10.0.22621.5472, Windows 11 23h
  4. To verify the build number, run 'winver' from the Run dialog or check System > About > Windows specification
Caveat Standard Windows update applies; ensure backups and system state backups exist before applying updates in production environments

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1507 Exploited in the wild — priority engagement
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-33073 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-33073 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data