CVE-2020-0796

CRITICALNVD 10.010.0
EchelonGraph scoreHIGH confidence

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.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, ghsa, nvd
Trending — 3 sources updated this weekExploited in the wild
10.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS PROB: 100%CVSS: 10.0Exploit: cisa kev · ssvc active · kev ransomware · Metasploit · epss top5pct · epss high · public exploitExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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'.

CVSS v3
10.0
EG Score
10.0(high)
EG Risk
100(Act)
EG Risk 100/100SSVC: Act

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 computed
Severity100% × 45%
Exploitation100% × 40%
Automatability100% × 15%
Action: Fix now — active exploitation, automatable, high impact.
EPSS PROB
100%
EPSS %ILE
100%
KEV
⚠ Exploited

Published

March 12, 2020

Last Modified

August 12, 2026

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 85× in last 7d / 320× 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 953 total refreshes for this CVE.

  1. 2026-08-22 00:29 UTCVendor advisory
  2. 2026-08-22 00:29 UTCGHSA enrichment
  3. 2026-08-21 20:27 UTCGHSA enrichment
  4. 2026-08-21 16:49 UTCCISA KEV update
  5. 2026-08-21 16:24 UTCGHSA enrichment
  6. 2026-08-21 12:21 UTCVendor advisory
  7. 2026-08-21 12:21 UTCGHSA enrichment
  8. 2026-08-21 08:18 UTCVendor advisory
  9. 2026-08-21 08:18 UTCGHSA enrichment
  10. 2026-08-21 04:15 UTCVendor advisory
  11. 2026-08-21 04:15 UTCGHSA enrichment
  12. 2026-08-21 00:12 UTCVendor advisory
  13. 2026-08-21 00:12 UTCGHSA enrichment
  14. 2026-08-20 20:09 UTCVendor advisory
  15. 2026-08-20 20:09 UTCGHSA enrichment
  16. 2026-08-20 17:06 UTCCISA KEV update
  17. 2026-08-20 16:06 UTCVendor advisory
  18. 2026-08-20 16:06 UTCGHSA enrichment
  19. 2026-08-20 12:03 UTCVendor advisory
  20. 2026-08-20 12:02 UTCGHSA enrichment
  21. 2026-08-20 07:59 UTCVendor advisory
  22. 2026-08-20 07:59 UTCGHSA enrichment
  23. 2026-08-20 03:57 UTCGHSA enrichment
  24. 2026-08-19 23:54 UTCVendor advisory
  25. 2026-08-19 23:54 UTCGHSA enrichment
Show 75 more
  1. 2026-08-19 19:51 UTCVendor advisory
  2. 2026-08-19 19:51 UTCGHSA enrichment
  3. 2026-08-19 17:33 UTCCISA KEV update
  4. 2026-08-19 15:48 UTCVendor advisory
  5. 2026-08-19 15:48 UTCGHSA enrichment
  6. 2026-08-19 11:44 UTCVendor advisory
  7. 2026-08-19 11:44 UTCGHSA enrichment
  8. 2026-08-19 07:40 UTCVendor advisory
  9. 2026-08-19 07:40 UTCGHSA enrichment
  10. 2026-08-19 03:37 UTCVendor advisory
  11. 2026-08-19 03:37 UTCGHSA enrichment
  12. 2026-08-18 23:35 UTCVendor advisory
  13. 2026-08-18 23:34 UTCGHSA enrichment
  14. 2026-08-18 19:32 UTCVendor advisory
  15. 2026-08-18 19:32 UTCGHSA enrichment
  16. 2026-08-18 16:58 UTCCISA KEV update
  17. 2026-08-18 15:28 UTCVendor advisory
  18. 2026-08-18 15:28 UTCGHSA enrichment
  19. 2026-08-18 11:22 UTCVendor advisory
  20. 2026-08-18 11:22 UTCGHSA enrichment
  21. 2026-08-18 07:19 UTCGHSA enrichment
  22. 2026-08-18 03:16 UTCVendor advisory
  23. 2026-08-18 03:16 UTCGHSA enrichment
  24. 2026-08-17 23:11 UTCVendor advisory
  25. 2026-08-17 23:11 UTCGHSA enrichment
  26. 2026-08-17 19:08 UTCVendor advisory
  27. 2026-08-17 19:08 UTCGHSA enrichment
  28. 2026-08-17 15:03 UTCVendor advisory
  29. 2026-08-17 15:03 UTCGHSA enrichment
  30. 2026-08-17 13:56 UTCCISA KEV update
  31. 2026-08-17 11:00 UTCVendor advisory
  32. 2026-08-17 11:00 UTCGHSA enrichment
  33. 2026-08-17 06:57 UTCVendor advisory
  34. 2026-08-17 06:57 UTCGHSA enrichment
  35. 2026-08-17 02:55 UTCVendor advisory
  36. 2026-08-17 02:55 UTCGHSA enrichment
  37. 2026-08-16 22:52 UTCVendor advisory
  38. 2026-08-16 22:52 UTCGHSA enrichment
  39. 2026-08-16 18:49 UTCVendor advisory
  40. 2026-08-16 18:49 UTCGHSA enrichment
  41. 2026-08-16 14:46 UTCVendor advisory
  42. 2026-08-16 14:46 UTCGHSA enrichment
  43. 2026-08-16 10:43 UTCVendor advisory
  44. 2026-08-16 10:43 UTCGHSA enrichment
  45. 2026-08-16 06:40 UTCVendor advisory
  46. 2026-08-16 06:40 UTCGHSA enrichment
  47. 2026-08-16 02:37 UTCVendor advisory
  48. 2026-08-16 02:37 UTCGHSA enrichment
  49. 2026-08-15 22:35 UTCVendor advisory
  50. 2026-08-15 22:35 UTCGHSA enrichment
  51. 2026-08-15 18:32 UTCVendor advisory
  52. 2026-08-15 18:32 UTCGHSA enrichment
  53. 2026-08-15 14:29 UTCVendor advisory
  54. 2026-08-15 14:29 UTCGHSA enrichment
  55. 2026-08-15 10:26 UTCVendor advisory
  56. 2026-08-15 10:26 UTCGHSA enrichment
  57. 2026-08-15 06:23 UTCVendor advisory
  58. 2026-08-15 06:23 UTCGHSA enrichment
  59. 2026-08-15 02:04 UTCVendor advisory
  60. 2026-08-15 02:04 UTCGHSA enrichment
  61. 2026-08-14 22:02 UTCVendor advisory
  62. 2026-08-14 22:02 UTCGHSA enrichment
  63. 2026-08-14 17:59 UTCVendor advisory
  64. 2026-08-14 17:59 UTCGHSA enrichment
  65. 2026-08-14 13:57 UTCVendor advisory
  66. 2026-08-14 13:57 UTCGHSA enrichment
  67. 2026-08-14 09:54 UTCGHSA enrichment
  68. 2026-08-14 05:52 UTCVendor advisory
  69. 2026-08-14 05:52 UTCGHSA enrichment
  70. 2026-08-14 01:49 UTCVendor advisory
  71. 2026-08-14 01:49 UTCGHSA enrichment
  72. 2026-08-13 21:46 UTCVendor advisory
  73. 2026-08-13 21:46 UTCGHSA enrichment
  74. 2026-08-13 17:43 UTCVendor advisory
  75. 2026-08-13 17:43 UTCGHSA enrichment

Publicly available exploits

(10 references)

Working exploit code is in the public domain (7 GitHub PoCs) (3 Exploit-DB entries). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCrsmudge/CVE-2020-0796-BOF
    First seen Sep 17, 2020
    Open source ↗
  • GitHub PoCBarriuso/SMBGhost_AutomateExploitation
    First seen Jun 10, 2020

    SMBGhost (CVE-2020-0796) Automate Exploitation and Detection

    Open source ↗
  • Exploit-DBEDB-48537
    First seen Jun 2, 2020

    Microsoft Windows - 'SMBGhost' Remote Code Execution

    Open source ↗
  • GitHub PoCjamf/CVE-2020-0796-RCE-POC
    First seen Apr 20, 2020

    CVE-2020-0796 Remote Code Execution POC

    Open source ↗
  • GitHub PoCRvn0xsy/CVE_2020_0796_CNA
    First seen Apr 6, 2020

    Cobalt Strike AggressorScripts CVE-2020-0796

    Open source ↗
  • GitHub PoCjiansiting/CVE-2020-0796
    First seen Apr 1, 2020
    Open source ↗
  • Exploit-DBEDB-48267
    First 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-0796
    First seen Mar 30, 2020

    CVE-2020-0796 - Windows SMBv3 LPE exploit #SMBGhost

    Open source ↗
  • GitHub PoCjamf/CVE-2020-0796-LPE-POC
    First seen Mar 30, 2020

    CVE-2020-0796 Local Privilege Escalation POC

    Open source ↗
  • Exploit-DBEDB-48216
    First seen Mar 14, 2020

    Microsoft Windows 10 (1903/1909) - 'SMBGhost' SMB3.1.1 'SMB2_COMPRESSION_CAPABILITIES' Buffer Overflow (PoC)

    Open source ↗

Frequently asked(6)

What is CVE-2020-0796?
CVE-2020-0796 is a critical vulnerability published on March 12, 2020. 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'.
When was CVE-2020-0796 disclosed?
CVE-2020-0796 was first published in the National Vulnerability Database on March 12, 2020, with the most recent update on August 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2020-0796 actively exploited?
Yes. CISA added CVE-2020-0796 to the Known Exploited Vulnerabilities catalog on February 10, 2022, affecting Microsoft SMBv3. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate patching attention.
What is the CVSS score of CVE-2020-0796?
CVE-2020-0796 has a CVSS v3 base score of 10.0 (NVD).
Which products are affected by CVE-2020-0796?
CVE-2020-0796 affects Microsoft SMBv3. The full affected-products list, including version ranges and fixed versions, is shown in the Affected Packages section of this page.
How do I remediate CVE-2020-0796?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-0796, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2020-0796

Explore →

Is Your Infrastructure Affected by CVE-2020-0796?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.