cve.bz

CVE-2020-0796 (SMBGhost) Microsoft SMBv3 Remote Code Execution Vulnerability

10.0 criticalKEVExploitEPSS 99.8%Fix available

Critical (10.0) in Microsoft SMBv3. In CISA KEV since 2022-02-10, with known ransomware use. EPSS 99.8% estimated probability of exploitation activity in the next 30 days.

On this page
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'.

Severity

CVSS 3.1

10.0 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
EPSS
99.8% (unchanged from 99.8% a week ago; 99.8% 30 days ago) estimated probability of exploitation activity in the next 30 days; 100th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA KEV
listed 2022-02-10, due 2022-08-10, known ransomware use
CISA's assessment (SSVC)
Exploitation: active · Automatable: yes · Technical impact: total, assessed 2026-08-12. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2020-0796 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2020-0796?via=ask-ai-copy and https://cve.bz/cve/CVE-2020-0796?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2020-0796 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2020-0796

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2020-0796](https://cve.bz/cve/badge/CVE-2020-0796.svg)](https://cve.bz/cve/CVE-2020-0796)

HTML:

<a href="https://cve.bz/cve/CVE-2020-0796"><img src="https://cve.bz/cve/badge/CVE-2020-0796.svg" alt="CVE-2020-0796"></a>

Affected

Public exploits

GitHub PoC (unverified)

Repositories on GitHub named after this CVE. Nobody has checked them and they are not scanned: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-119 (12).

References

Check your stackJSON