CVE-2020-0796: SMBGhost
- Vendor
- Microsoft Corporation
SMBGhost is an integer overflow vulnerability in Microsoft SMB 3.1.1 compression handling affecting Windows 10 versions 1903 and 1909 and Windows Server versions 1903 and 1909. In the server-side Srv2DecompressData function, attacker-controlled OriginalCompressedSegmentSize and Offset values from an SMB2_COMPRESSION_TRANSFORM_HEADER are added without adequate bounds checking. The 32-bit sum can wrap around, causing SrvNetAllocateBuffer to allocate an undersized kernel heap buffer. Subsequent decompression can overrun that buffer and corrupt adjacent kernel memory. The vulnerability permits unauthenticated remote code execution against affected SMB servers and clients and can also be exploited for local privilege escalation.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation can execute arbitrary code with SYSTEM privileges and give an attacker full control of an affected system, compromising confidentiality and integrity. Kernel memory corruption can also crash the system and disrupt services. The unauthenticated server-side attack path creates potential for worm-like propagation and lateral movement among reachable vulnerable systems.
Mitigation
If you can’t patch tonight, do this now.
Until patching is complete, disable SMBv3 compression on servers by setting the LanmanServer Parameters DisableCompression DWORD value to 1. This workaround does not require a reboot and protects only the server-side attack path; it does not protect vulnerable SMB clients. Block inbound TCP port 445 from the internet and restrict outbound TCP port 445 to prevent connections to untrusted SMB servers. Perimeter filtering does not prevent exploitation originating within the internal network. SMBv3 compression can be re-enabled after patching.
Remediation
Patch, then assume compromise.
Install Microsoft's security update for CVE-2020-0796, released on March 12, 2020, or a superseding update covering the vulnerability, on every affected Windows client and server. Reboot affected systems to complete installation and verify that the update is effective.
Exploits
27 exploits validated by Mallory's analysis. Hidden: 16 rejected by Mallory's analysis as not a working exploit; 4 not yet analyzed, such as Exploit-DB entries. Showing the 25 most capable, earliest first.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2020-0796 exploited in the wild?
- Yes. As of Nov 9, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Feb 10, 2022.
- Is there a public exploit for CVE-2020-0796?
- Yes. Mallory tracks 27 public exploits or proofs of concept for CVE-2020-0796, the earliest disclosed Nov 19, 2019.
- Is there a patch for CVE-2020-0796?
- Install Microsoft's security update for CVE-2020-0796, released on March 12, 2020, or a superseding update covering the vulnerability, on every affected Windows client and server. Reboot affected systems to complete installation and verify that the update is effective.
- What products are affected by CVE-2020-0796?
- Microsoft Corporation Windows 10 1903, Microsoft Corporation Windows 10 1909, Microsoft Corporation Windows Server 1903, and Microsoft Corporation Windows Server 1909.
- How severe is CVE-2020-0796?
- CVE-2020-0796 has a CVSS v3.1 score of 10.0 (Critical) and an EPSS score of 99.8% (100th percentile) as of Nov 9, 2026.
Recent activity
44 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.