CVE-2020-0796Known ransomware useCRITICAL · 10.0Patch first

Microsoft SMBv3 Remote Code Execution Vulnerability

CVE-2020-0796 is a security vulnerability in Microsoft SMBv3, added to CISA KEV on February 10, 2022. Patch order: first of four. Known ransomware use: yes.

Added to CISA KEV · Updated · Microsoft SMBv3

What is CVE-2020-0796?

A remote code execution vulnerability exists in the way that the Microsoft Server Message Block 3.1.1 (SMBv3) protocol handles certain requests. An attacker who successfully exploited the vulnerability could gain the ability to execute code on the target server or client.

Known to be used in ransomware campaigns. Active threat actors have chained this vulnerability into ransomware operations — treat patching as a same-week priority, not a "next maintenance window" task. The fix is the same one below; the urgency is higher.

VulnCheck tracked exploitation 624 days before CISA's KEV listing. VulnCheck's broader catalog of in-the-wild exploitation evidence picked this up before it landed on CISA's formal list. Per-CVE fact about this entry; not a population claim about lead time in general.

Who is affected by CVE-2020-0796?

Affects anyone running Microsoft SMBv3. Microsoft products in a small practice typically sit close to credentials, email, or document workflows — treat the patch as in-scope.

What should I do about CVE-2020-0796?

Apply updates per vendor instructions.

If you don't have someone in-house to verify the patch deployed across every endpoint — or you're not sure whether you're affected — that's exactly the kind of triage we do. Request a free review.

Insurance readiness

Your insurer will ask if this is patched.

Unpatched entries on CISA's Known Exploited Vulnerabilities list are exactly what cyber-insurance carrier questionnaires probe for, and knowing which controls they check is how you keep a renewal from stalling.

Get the free carrier questionnaire →

Severity

CVSS base score: 10.0 — CRITICAL

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

Weakness classification: CWE-119

CVSS, severity, and CWE data from the National Vulnerability Database (NVD). This product uses data from the NVD API but is not endorsed or certified by the NVD.

Microsoft fix

  • KB4551762 (Security Update)

Microsoft Exploitability Index (assessed at update release): Exploitation More Likely

This CVE is on CISA's Known Exploited Vulnerabilities catalog. Microsoft's index reflects their release-time forecast, not current observed activity, and is not automatically revised upward when exploitation appears later.

Sourced from Microsoft Security Update Guide (CVRF document 2020-Mar).

Vendor workaround

Vendor-published workaround

The following workaround may be helpful in your situation. In all cases, Microsoft strongly recommends that you install the updates for this vulnerability as soon as they become available even if you plan to leave this workaround in place:

Disable SMBv3 compression

You can disable compression to block unauthenticated attackers from exploiting the vulnerability against an SMBv3 Server with the PowerShell command below.

Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters" DisableCompression -Type DWORD -Value 1 -Force

Notes:

  1. No reboot is needed after making the change.
  2. This workaround does not prevent exploitation of SMB clients; please see item 2 under FAQ to protect clients.
  3. SMB Compression is not yet used by Windows or Windows Server, and disabling SMB Compression has no negative performance impact.

You can disable the workaround with the PowerShell command below.

Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters" DisableCompression -Type DWORD -Value 0 -Force

Note: No reboot is needed after disabling the workaround.

A workaround reduces exposure while you patch — it is not a substitute for the update. Install the fix above as soon as you can.

Shown as published by Microsoft (Security Update Guide, CVRF document 2020-Mar); formatting sanitized, content unaltered.

CISA due date

CISA's listed due date: August 10, 2022.

Federal civilian agencies work under CISA's Binding Operational Directive 26-04, which replaced BOD 22-01 on June 10, 2026. It sets the deadline for each affected system by:

  • How exposed that system is to the internet
  • Whether the attack can be automated
  • How much control it gives an attacker

Its table gives catalogued vulnerabilities 3 or 14 days.

None of this binds a private business, but treat the date as a strong recommendation, especially if you handle regulated data (HIPAA, GLBA, ABA model rules).

EPSS

EPSS score: 99.8% — higher than 100% of all scored CVEs.

EPSS estimates the probability of exploitation activity in the next 30 days. Every entry on this site is already confirmed exploited, so read it as relative urgency among the things you still have open, not as permission to wait.

Score dated 2026-10-15, from the FIRST.org Exploit Prediction Scoring System.

Source

This entry comes from CISA's Known Exploited Vulnerabilities catalog, public US-Government data we pull daily. The plain-language framing and the what-to-do guidance above are ours. View the original entry on cisa.gov.

Weekly digest

Get the weekly digest in your inbox.

Drop your email and we send you what changed in your watch each week. If nothing changed, we tell you that too.

Watching: Microsoft