Skip to content
Server Security Center
KEVcritical10.0 Used in ransomware campaigns

CVE-2020-0796: Microsoft SMBv3 Remote Code Execution

Microsoft SMBv3 · listed in the CISA catalog of actively exploited vulnerabilities since 2022-02-10.

CVSS v3.1 (CISA ADP)
10.0
critical
EPSS (exploit probability, 30 days)
99.8%
among the highest 0.1% of all CVEs
Added to CISA KEV
2022-02-10
US federal due date 2022-08-10
Automatable (CISA SSVC)
yes
technical impact: total

CVE-2020-0796 explained

CVE-2020-0796 is a remote code execution vulnerability in how the Microsoft Server Message Block 3.1.1 (SMBv3) protocol handles certain requests in Windows. It affects both the SMBv3 client and server. CISA lists it as known exploited, including in ransomware campaigns, which makes patching urgent.

Impact

An unauthenticated attacker with network access can run code on an affected system without user interaction. The flaw is a memory buffer handling weakness. CISA rates it automatable, meaning it can be exploited at scale, with total technical impact: full control of the affected component. Confidentiality, integrity and availability impacts are all high, and the impact can extend beyond the vulnerable component. Attackers are known to exploit it, including for ransomware.

Who is affected

The CVE record lists Microsoft Windows 10 Version 1903 and Version 1909 for 32-bit, x64-based and ARM64-based Systems, plus Microsoft Windows Server, version 1903 (Server Core installation) and Microsoft Windows Server, version 1909 (Server Core installation). The record names the affected products but no specific versions, and it names no fixed version. Consult the Microsoft advisory for the updates that address the issue.

Written with AI from the data on this page and checked against it automatically.

Official description

A remote code execution vulnerability exists in the way that the Microsoft Server Message Block 3.1.1 (SMBv3) protocol handles certain requests, aka 'Windows SMBv3 Client/Server Remote Code Execution Vulnerability'.

CISA required action: Apply updates per vendor instructions.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • Microsoft Windows 10 Version 1903 for 32-bit Systems
    Affected
    –
    Fixed in
    not stated

    Affected versions are not specified in the CVE record.

  • Microsoft Windows 10 Version 1903 for x64-based Systems
    Affected
    –
    Fixed in
    not stated

    Affected versions are not specified in the CVE record.

  • Microsoft Windows 10 Version 1903 for ARM64-based Systems
    Affected
    –
    Fixed in
    not stated

    Affected versions are not specified in the CVE record.

  • Microsoft Windows Server, version 1903 (Server Core installation)
    Affected
    –
    Fixed in
    not stated

    Affected versions are not specified in the CVE record.

  • Microsoft Windows 10 Version 1909 for 32-bit Systems
    Affected
    –
    Fixed in
    not stated

    Affected versions are not specified in the CVE record.

  • Microsoft Windows 10 Version 1909 for x64-based Systems
    Affected
    –
    Fixed in
    not stated

    Affected versions are not specified in the CVE record.

  • Microsoft Windows 10 Version 1909 for ARM64-based Systems
    Affected
    –
    Fixed in
    not stated

    Affected versions are not specified in the CVE record.

  • Microsoft Windows Server, version 1909 (Server Core installation)
    Affected
    –
    Fixed in
    not stated

    Affected versions are not specified in the CVE record.

How to fix it

  • The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
  • Vendor advisory: portal.msrc.microsoft.com/en-US/security-guidance/advisor…
  • CISA's deadline for US federal agencies: 2022-08-10 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Apply the Microsoft security updates for this vulnerability on all affected Windows 10 and Windows Server systems, as CISA's required action states.
  2. Identify every system running Windows 10 or Windows Server version 1903 or 1909, including Server Core installations.
  3. Block SMB traffic from the internet at the network perimeter and restrict SMB access between internal network segments.
  4. Follow any workarounds in the Microsoft advisory for systems that cannot be updated immediately.
  5. Check exposed and unpatched systems for signs of compromise, given known ransomware use.

The CVE record names no fixed version. Follow the Microsoft advisory, which identifies the security updates for each affected product, and meet CISA's required action to apply updates per vendor instructions. Until updates are in place, block SMB from untrusted networks, apply any vendor workarounds and monitor affected systems for signs of compromise.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
Yes – attackers can automate it at scale
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

Questions about CVE-2020-0796

Is CVE-2020-0796 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-02-10 and notes known use in ransomware campaigns. The US federal due date for remediation was 2022-08-10.
Does an attacker need credentials or user interaction?
No. The attack works over the network with low complexity, requires no privileges and no user interaction. CISA also rates it automatable.
Are both SMB clients and servers affected?
Yes. The vulnerability is also known as the Windows SMBv3 Client/Server Remote Code Execution Vulnerability, so both roles on affected Windows versions need the update.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.