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'.
CVE-2020-0796
Score elevated to 10.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2022-02-10), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 10.0 retained for reference. Confidence: HIGH.
- Actively exploited in the wild (CISA-KEV)
A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).
- CVSS v3
- 10.0
- EG Score
- 10.0CRITICALhigh confidence
- EG Risk
- 100EG Risk 100/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity100% × 45%Exploitation100% × 40%Automatability100% × 15%CISA SSVC: Attend at low mission impact; Act at medium or high.Action: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that sooner than your standard update timelines at low mission impact and as soon as possible at medium or high; until then, restrict network exposure of the affected system or apply the vendor's mitigation. - EPSS PROB
- 100%
- EPSS %ILE
- 99th
- KEV
- ⚠ Exploited
CISA SSVCAttend at low mission impact; Act at medium or high.
A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that sooner than your standard update timelines at low mission impact and as soon as possible at medium or high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
March 12, 2020
Last Modified
October 1, 2026
Advisory Details (7)
Auto-updated Oct 1, 2026Packet Storm - Human Validation
http://packetstormsecurity.com/files/156980/Microsoft-Windows-10-SMB-3.1.1-Local-Privilege-Escalation.htmlPacket Storm - Human Validation
http://packetstormsecurity.com/files/156732/Microsoft-Windows-SMB-3.1.1-Remote-Code-Execution.htmlPacket Storm - Human Validation
http://packetstormsecurity.com/files/156731/CoronaBlue-SMBGhost-Microsoft-Windows-10-SMB-3.1.1-Proof-Of-Concept.htmlSecurity Update Guide - Microsoft Security Response Center
Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update
https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2020-0796Packet Storm - Human Validation
http://packetstormsecurity.com/files/158054/SMBleed-SMBGhost-Pre-Authentication-Remote-Code-Execution-Proof-Of-Concept.htmlPacket Storm - Human Validation
http://packetstormsecurity.com/files/157901/Microsoft-Windows-SMBGhost-Remote-Code-Execution.htmlPacket Storm - Human Validation
http://packetstormsecurity.com/files/157110/SMBv3-Compression-Buffer-Overflow.htmlVendor Advisories for CVE-2020-0796(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 93× in last 7d / 379× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 1,523 total refreshes for this CVE.
- 2026-10-06 06:01 UTCVendor advisory
- 2026-10-06 05:57 UTCVendor advisory
- 2026-10-06 05:57 UTCVendor advisory
- 2026-10-06 05:57 UTCGHSA enrichment
- 2026-10-06 05:53 UTCVendor advisory
- 2026-10-06 05:52 UTCVendor advisory
- 2026-10-06 05:52 UTCGHSA enrichment
- 2026-10-06 05:48 UTCGHSA enrichment
- 2026-10-06 05:46 UTCNVD updatefirst tracked
- 2026-10-06 01:45 UTCVendor advisory
- 2026-10-06 01:45 UTCGHSA enrichment
- 2026-10-05 21:42 UTCVendor advisory
- 2026-10-05 21:41 UTCGHSA enrichment
- 2026-10-05 17:35 UTCVendor advisory
- 2026-10-05 17:35 UTCGHSA enrichment
- 2026-10-05 13:33 UTCVendor advisory
- 2026-10-05 13:32 UTCGHSA enrichment
- 2026-10-05 09:28 UTCVendor advisory
- 2026-10-05 09:28 UTCGHSA enrichment
- 2026-10-05 05:25 UTCVendor advisory
- 2026-10-05 05:25 UTCGHSA enrichment
- 2026-10-05 01:22 UTCVendor advisory
- 2026-10-05 01:22 UTCGHSA enrichment
- 2026-10-04 21:19 UTCVendor advisory
- 2026-10-04 21:19 UTCGHSA enrichment
Show 75 moreShow fewer
- 2026-10-04 17:16 UTCVendor advisory
- 2026-10-04 17:16 UTCGHSA enrichment
- 2026-10-04 13:13 UTCVendor advisory
- 2026-10-04 13:13 UTCGHSA enrichment
- 2026-10-04 09:11 UTCVendor advisory
- 2026-10-04 09:10 UTCGHSA enrichment
- 2026-10-04 05:07 UTCVendor advisory
- 2026-10-04 05:07 UTCGHSA enrichment
- 2026-10-04 01:05 UTCVendor advisory
- 2026-10-04 01:05 UTCGHSA enrichment
- 2026-10-03 21:01 UTCVendor advisory
- 2026-10-03 21:01 UTCGHSA enrichment
- 2026-10-03 16:58 UTCVendor advisory
- 2026-10-03 16:58 UTCGHSA enrichment
- 2026-10-03 12:55 UTCVendor advisory
- 2026-10-03 12:55 UTCGHSA enrichment
- 2026-10-03 08:52 UTCVendor advisory
- 2026-10-03 08:52 UTCGHSA enrichment
- 2026-10-03 04:49 UTCVendor advisory
- 2026-10-03 04:49 UTCGHSA enrichment
- 2026-10-03 00:46 UTCVendor advisory
- 2026-10-03 00:46 UTCGHSA enrichment
- 2026-10-02 20:43 UTCVendor advisory
- 2026-10-02 20:43 UTCGHSA enrichment
- 2026-10-02 16:40 UTCVendor advisory
- 2026-10-02 16:40 UTCGHSA enrichment
- 2026-10-02 12:34 UTCVendor advisory
- 2026-10-02 12:34 UTCGHSA enrichment
- 2026-10-02 08:32 UTCVendor advisory
- 2026-10-02 08:32 UTCGHSA enrichment
- 2026-10-02 04:29 UTCVendor advisory
- 2026-10-02 04:28 UTCGHSA enrichment
- 2026-10-02 00:25 UTCVendor advisory
- 2026-10-02 00:25 UTCGHSA enrichment
- 2026-10-01 20:23 UTCVendor advisory
- 2026-10-01 20:22 UTCGHSA enrichment
- 2026-10-01 20:01 UTCEG score recompute
- 2026-10-01 20:01 UTCVendor advisory
- 2026-10-01 20:01 UTCGHSA enrichment
- 2026-10-01 18:47 UTCVendor advisory
- 2026-10-01 18:47 UTCGHSA enrichment
- 2026-10-01 14:44 UTCVendor advisory
- 2026-10-01 14:44 UTCGHSA enrichment
- 2026-10-01 10:41 UTCVendor advisory
- 2026-10-01 10:41 UTCGHSA enrichment
- 2026-10-01 06:38 UTCVendor advisory
- 2026-10-01 06:38 UTCGHSA enrichment
- 2026-10-01 02:35 UTCVendor advisory
- 2026-10-01 02:35 UTCGHSA enrichment
- 2026-09-30 22:32 UTCVendor advisory
- 2026-09-30 22:32 UTCGHSA enrichment
- 2026-09-30 18:29 UTCGHSA enrichment
- 2026-09-30 14:25 UTCVendor advisory
- 2026-09-30 14:25 UTCGHSA enrichment
- 2026-09-30 10:19 UTCVendor advisory
- 2026-09-30 10:19 UTCGHSA enrichment
- 2026-09-30 06:14 UTCVendor advisory
- 2026-09-30 06:14 UTCGHSA enrichment
- 2026-09-30 02:10 UTCVendor advisory
- 2026-09-30 02:10 UTCGHSA enrichment
- 2026-09-29 22:07 UTCVendor advisory
- 2026-09-29 22:07 UTCGHSA enrichment
- 2026-09-29 18:03 UTCVendor advisory
- 2026-09-29 18:03 UTCGHSA enrichment
- 2026-09-29 13:56 UTCVendor advisory
- 2026-09-29 13:56 UTCGHSA enrichment
- 2026-09-29 09:53 UTCVendor advisory
- 2026-09-29 09:53 UTCGHSA enrichment
- 2026-09-29 05:50 UTCVendor advisory
- 2026-09-29 05:50 UTCGHSA enrichment
- 2026-09-29 01:47 UTCVendor advisory
- 2026-09-29 01:47 UTCGHSA enrichment
- 2026-09-28 21:44 UTCEG score recompute
- 2026-09-28 21:44 UTCVendor advisory
- 2026-09-28 21:44 UTCGHSA enrichment
Publicly available exploits
(10 references)Working exploit code is in the public domain (2 Metasploit modules) (6 GitHub PoCs) (2 Exploit-DB entries). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- Metasploitexploit/windows/local/cve_2020_0796_smbghost✓ verifiedFirst seen Mar 13, 2020
SMBv3 Compression Buffer Overflow
Open source ↗ - Metasploitexploit/windows/smb/cve_2020_0796_smbghost✓ verifiedFirst seen Mar 13, 2020
SMBv3 Compression Buffer Overflow
Open source ↗ - Open source ↗GitHub PoCrsmudge/CVE-2020-0796-BOFFirst seen Sep 17, 2020
- GitHub PoCBarriuso/SMBGhost_AutomateExploitationFirst seen Jun 10, 2020
SMBGhost (CVE-2020-0796) Automate Exploitation and Detection
Open source ↗ - Exploit-DBEDB-48537First seen Jun 2, 2020
Microsoft Windows - 'SMBGhost' Remote Code Execution
Open source ↗ - GitHub PoCjamf/CVE-2020-0796-RCE-POCFirst seen Apr 20, 2020
CVE-2020-0796 Remote Code Execution POC
Open source ↗ - GitHub PoCRvn0xsy/CVE_2020_0796_CNAFirst seen Apr 6, 2020
Cobalt Strike AggressorScripts CVE-2020-0796
Open source ↗ - Open source ↗GitHub PoCjiansiting/CVE-2020-0796First seen Apr 1, 2020
- Exploit-DBEDB-48267First seen Mar 30, 2020
Microsoft Windows 10 (1903/1909) - 'SMBGhost' SMB3.1.1 'SMB2_COMPRESSION_CAPABILITIES' Local Privilege Escalation
Open source ↗ - GitHub PoCdanigargu/CVE-2020-0796First seen Mar 30, 2020
CVE-2020-0796 - Windows SMBv3 LPE exploit #SMBGhost
Open source ↗
Related CVEs(same CWE)
Same CWE
10 shownCWE-119 · CWE-20
Frequently asked(6)
What is CVE-2020-0796?
When was CVE-2020-0796 disclosed?
Is CVE-2020-0796 actively exploited?
What is the CVSS score of CVE-2020-0796?
Which products are affected by CVE-2020-0796?
How do I remediate CVE-2020-0796?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2020-0796
Is Your Infrastructure Affected by CVE-2020-0796?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.