vciy

CVE-2020-0796 · SMBGhost

INDEX BUILT · 2026-09-20

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

A remote code execution vulnerability exists in the way that the Microsoft Server Message Block 3.1.1 (SMBv3) protocol handles certain requests, aka…

CVE-2020-07963 of 4 sources documented this
71

rank 71 = 40 + 25 + 0 + 0 + 6

rank@v1 · act now

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.99810 · CISA KEV listed  ·  without this subject the record ranks 31

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 10.0, from NVD  ·  without this subject the record ranks 46

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

no persisting rise in 365 days  ·  without this subject the record ranks 71

How much of the world it touches

NVD CPE configurations

0 products in the CPE ranges  ·  without this subject the record ranks 71

Someone else already set the date

CISA KEV remediation due date

CISA remediation date held  ·  without this subject the record ranks 65

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$4.98Mover the next 30 days, if this record is yours
Movementno material movementthe record holds only daily drift and scoring model releases
Basisassumeda published average, not your estate

$4.98M = $4.99M incident cost x 1 exposure x 0.9981 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Hindsight · the state

0.9981EPSSKEV · LISTED
Severity10 CRITICALreceipt
Harmtotal loss · unauthenticated · ransomware-linkedreceipt
Exploitationransomware use knownreceipt
Defenseno fix version held
Movementscoring model changedreceipt
PLATEAU10Minimal movement since 2021-04-14, 1969 days at 1.00, as of 2026-09-04. arc-rules@v1

Foresight · where to check next

CVE-2020-29557BIG-IPCitrix NetScalerMicrosoftMicrosoft OfficeGoogle Chrome0796

This record is one instance of CWE-119, improper restriction of operations within the bounds of a memory buffer. The index holds 14296 prior instances of this class, 56 KEV-listed. The nearest of its KEV-listed records are drawn beside this. taxonomy@v1

Full pattern panel

Prior records in this weakness class. Each is its own record, dated and receipted.
Color is a claim, not decoration:the hostile worldthe defenseno signalspoke length is how much of the record matches, not how bad it is

Running Microsoft Windows 10 Version 1903 for…? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Set up a watchlist (needs a Practitioner account)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

AcceptDeferPatch by…Not affectedMitigated

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

Reachnetwork-reachable · no privileges required · no user interaction · low attack complexityreceipt
ImpactComplete confidentiality, integrity and availability loss, with impact beyond the vulnerable componentreceipt
Scored fromCVSS v3.1 · NVD's vectorreceipt
Weakness classCWE-119 Improper Restriction of Operations within the Bounds of a Memory Bufferreceipt
Published consequencesCWE-119: Integrity, Confidentiality, Availability: Execute Unauthorized Code or Commands, Modify Memory; Availability, Confidentiality: Read Memory, DoS: Crash, Exit, or Restart, DoS: Resource…[email protected]
Ransomware campaign useKnown (CISA)receipt

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

Fixed inNo fix version in held sources, as the index stood on 4 Sep 2026.
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.
CISA remediation statusoverdue since 2022-08-10receipt
CISA required actionApply updates per vendor instructions.receipt
Published to CISA KEV700 daysderived

Exploit Status & Known PoCs a ladder, not a score

Current rung: Ransomware campaign use known, 2022-02-10.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published · 88 public repositories2019-11-19receipt
  • RUNG 3Exploited in the wild · CISA KEV listed2022-02-10receipt
  • RUNG 4Ransomware campaign use known2022-02-10receipt

Authority who says so

CVSS, NVD10 CRITICALreceipt
Exploit probability0.9981 · top 0.04% of all CVEsreceipt
Assigned bymicrosoftreceipt
Recorded changes63 · last 9 Sep 2026derived

Affected & Fixed Versions as published

Affected productMicrosoft Windows 10 Version 1903 for 32-bit Systems; Microsoft Windows 10 Version 1903 for x64-based Systems; Microsoft Windows 10 Version 1903 for ARM64-based Systems…receipt

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

What it is stated by the CNA

SMBGhost is the common name for 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, aka 'Windows SMBv3 Client/Server Remote Code Execution Vulnerability'. cve-aliases@2026-08-27

NVD's analysis a second authority

severity
10 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
weakness
CWE-119
also scored by
10 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

check it yourself portal.msrc.microsoft.com packetstormsecurity.com packetstormsecurity.com packetstormsecurity.com packetstormsecurity.com packetstormsecurity.com +1 morereceipt

Dated events

2022-02-10Added to CISA KEV2022-08-10CISA remediation due2026-06-15EPSS moved 0.94 to 1.00

Movement the material steps

14 Apr 20210.93414
7 Mar 20230.97342 · scoring model v2023.03.01
17 Mar 20250.94419 · scoring model v2025.03.14
15 Jun 20260.9981 · scoring model v2026.06.15
Show all 49 observations
14 Apr 20210.93414
4 Feb 20220.95643
7 Mar 20230.97342
15 Apr 20230.97275
29 Apr 20230.97246
8 May 20230.97444
14 Jun 20230.97431
29 Jun 20230.97439
8 Jul 20230.97416
16 Jul 20230.97381
31 Jul 20230.97364
16 Aug 20230.97401
2 Sep 20230.97434
10 Nov 20230.97484
7 May 20240.97481
6 Jul 20240.97478
24 Jul 20240.97476
8 Aug 20240.97471
8 Sep 20240.97397
23 Sep 20240.97431
6 Oct 20240.97389
7 Nov 20240.97438
27 Nov 20240.97465
11 Dec 20240.97492
31 Dec 20240.97488
1 Feb 20250.97486
6 Mar 20250.97457
17 Mar 20250.94419
29 Jun 20250.94438
5 Jul 20250.94424
8 Jul 20250.94438
15 Jul 20250.94424
30 Jul 20250.94417
15 Sep 20250.94432
16 Sep 20250.94417
26 Sep 20250.94432
1 Oct 20250.94438
17 Oct 20250.94424
8 Nov 20250.94438
18 Nov 20250.94172
21 Nov 20250.94438
1 Dec 20250.94424
31 Dec 20250.94408
6 Mar 20260.94424
21 Mar 20260.94408
18 Apr 20260.94424
21 Apr 20260.94408
22 May 20260.94424
15 Jun 20260.9981

49 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.9981Public PoC2019-11-19Published2020-03-12CISA KEV2022-02-10Index as of2026-09-04

Listed by CISA 700 days after it published and the record had been public for 6 years, 5 months when this index was last written.

No material movement in 81 days as of the last ingest this index recorded.

Public PoC 2019-11-19 receipt · Published 2020-03-12 receipt · CISA KEV 2022-02-10 receipt · Index as of 2026-09-04 derived

The pattern, elsewhere

This record is one instance of CWE-119, improper restriction of operations within the bounds of a memory buffer. The index holds 14296 prior instances of this class, 56 KEV-listed. The nearest of its KEV-listed records are drawn beside this. [email protected]

CVE-2020-29557matches 7 of 8KEV listed · 2021receipt
CVE-2021-22991 · BIG-IPmatches 7 of 9KEV listed · 2021receipt
CVE-2023-4966 · Citrix NetScaler ADCmatches 6 of 9KEV listed · 2023receipt
CVE-2017-0101 · Microsoft Corporation Windowsmatches 6 of 9KEV listed · 2017receipt
CVE-2017-11882 · Microsoft Officematches 6 of 9KEV listed · 2017receipt
CVE-2026-3910 · Google Chromematches 6 of 9KEV listed · 2026receipt

"Matches n of m" counts the attributes the two records can both be compared on: the CVSS metrics they share a version of, any weakness class beyond this one, and the vendor. fit-rules@v1

14296 records in this class held. The six above are drawn from the ones CISA has listed as exploited, ranked by how much of the record matches this one. That is why every one of them is KEV-listed: the pool is, so the colour on those spokes says nothing the pool has not already said.

No curated product neighbourhood is held for this product, so the records above are the nearest this index can name. The neighbourhood table covers a small set of products and is extended by hand.

Siblings and hubs

Records related to this one

Browse the index from here

These are index-wide views, not findings about CVE-2020-0796.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.