Windows SMB Server CVE-2026-70133

Requires network reachability to the Windows SMB Server service (typically TCP 445). Per the CVSS vector (AV:N/AC:L/PR:N/UI:N) no authentication, no user interaction, and no special non-default configuration are stated - SMB Server is enabled by default on Windows Server roles and commonly reachable on internal networks. The practical limiting factor is network exposure: hosts whose SMB port is firewalled from untrusted networks or restricted to authenticated segments are far less exposed. Impact is confined to availability (service/host disruption); there is no path to data disclosure or code execution from this flaw.

This is a genuine but bounded network denial-of-service issue in Windows SMB Server. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, base 7.5) confirms an unauthenticated, low-complexity, network-reachable attack with no user interaction and pure availability impact - no confidentiality or integrity loss. Signals are largely consistent: CWE-770 (allocation of resources without limits or throttling) aligns with a resource-exhaustion DoS, and the SSVC decision (Exploitation: none, Automatable: yes, Technical Impact: partial) matches - 'Automatable: yes' is notable because an unauthenticated network DoS against a core OS service can be trivially scripted and repeated at scale, while 'Technical Impact: partial' and A:H-only reflect service disruption rather than full system compromise. Crucially, SSVC Exploitation is 'none', and there is no CISA KEV listing and no public POC, so this is not currently under active exploitation. EPSS is not provided in the input, so near-term exploitation probability cannot be quantified here. Bottom line: prioritize patching because the affected product is ubiquitous and the flaw is automatable and unauthenticated, but the real-world severity is capped at availability loss, not code execution or data exposure.

A remote, unauthenticated attacker with network access to TCP 445 sends crafted or high-volume SMB requests that cause the SMB Server to allocate resources without throttling, exhausting memory or handles until the service (or host) becomes unresponsive. No credentials or user interaction are required, and per SSVC the attack is automatable, so it can be scripted against many hosts. No public exploit identified at time of analysis.