vciy

CVE-2020-1167

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.

Microsoft Graphics Components Remote Code Execution Vulnerability

CVE-2020-11674 of 4 sources documented this
32

rank 32 = 1 + 23 + 1 + 7 + 0

rank@v1 · scheduled

Someone is already using it

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

EPSS 0.04716  ·  without this subject the record ranks 31

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 9.3, from NVD  ·  without this subject the record ranks 9

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

rose on 2025-07-16  ·  without this subject the record ranks 31

How much of the world it touches

NVD CPE configurations

7 products in the CPE ranges  ·  without this subject the record ranks 25

Someone else already set the date

CISA KEV remediation due date

no CISA due date  ·  without this subject the record ranks 32

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$235,000over the next 30 days, if this record is yours
Movement+$134,000on 2025-11-21, the last material move, 7 months before this reading
Basisassumeda published average, not your estate

$235,000 = $4.99M incident cost x 1 exposure x 0.04716 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.04716EPSSNOT IN KEVas of 2026-09-20
Severity7.8 HIGHreceipt
Harmtotal lossreceipt
Exploitationnone in held sources
Defenseno fix version held
Movementdoubled within 72hreceipt
PLATEAU10Minimal movement since 2025-03-30, 468 days at 0.05, as of 2026-07-11. arc-rules@v1

Foresight · where to check next

Microsoft WindowsMicrosoftMicrosoft WindowsMicrosoft 365CVE-2022-47966CVE-2022-294991167

This record is one instance of CWE-20, improper input validation. The index holds 13347 prior instances of this class, 73 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

Sources disagree here.

Severity score
Microsoft7.8 HIGHreceipt
NVD9.3 CRITICALreceipt
Scoring standard
MicrosoftCVSS v3.1receipt
NVDCVSS v2.0receipt

Both shown, dated. We don't pick winners. disagreement-rules@v1

Running Microsoft Windows 10 Version 1803? 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.

Reachneeds local access · no privileges required · user interaction required · low attack complexityreceipt
ImpactComplete confidentiality, integrity and availability lossreceipt
Scored fromCVSS v3.1 · the CNA's vectorreceipt
Weakness classCWE-20 Improper Input Validation; CWE-787 Out-of-bounds Writereceipt
Published consequencesCWE-20: Availability: DoS: Crash, Exit, or Restart, DoS: Resource Consumption (CPU), DoS: Resource Consumption (Memory); Confidentiality: Read Memory, Read Files or Directories…[email protected]

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 11 Jul 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.

Exploit Status & Known PoCs a ladder, not a score

Current rung: Nothing observed in held sources.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, the CNA7.8 HIGHreceipt
CVSS, NVD9.3 CRITICALreceipt
Exploit probability0.04716 · top 9% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned bymicrosoftreceipt
Recorded changes49 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productMicrosoft Windows 10 Version 1803; Microsoft Windows 10 Version 1809; Microsoft Windows Server 2019; Microsoft Windows 10 Version 1909; Microsoft Windows 10 Version 1709 for 32-bit Systems…receipt
Published rangesmicrosoft windows 10 1607; microsoft windows 10 1709; microsoft windows 10 1803; microsoft windows 10 1809receipt
Show all 7 published ranges
microsoft windows 10 1607
microsoft windows 10 1709
microsoft windows 10 1803
microsoft windows 10 1809
microsoft windows 10 1903
microsoft windows 10 1909
microsoft windows 10 2004

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

<p>A remote code execution vulnerability exists in the way that Microsoft Graphics Components handle objects in memory. An attacker who successfully exploited the vulnerability could execute arbitrary code on a target system.</p> <p>To exploit the vulnerability, a user would have to open a specially crafted file.</p> <p>The security update addresses the vulnerability by correcting how Microsoft Graphics Components handle objects in memory.</p> receipt

NVD's analysis a second authority

severity
9.3 AV:N/AC:M/Au:N/C:C/I:C/A:C
weakness
CWE-20; CWE-787
affected versions
microsoft windows 10 1607; microsoft windows 10 1709; microsoft windows 10 1803; and 4 more, listed in full below
also scored by
[email protected] 7.8 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H · [email protected] 7.8 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

The CNA scored it 7.8 and NVD 9.3. Both are shown because both were published; we do not pick one.

check it yourself portal.msrc.microsoft.com zerodayinitiative.com receipt

Dated events

2022-01-06EPSS moved 0.14 to 0.422026-06-15EPSS moved 0.11 to 0.04

Movement the material steps

14 Apr 20210.13741
6 Jan 20220.41682
4 Feb 20220.3168
1 Apr 20220.04475 · crossed 0.10
7 Mar 20230.00946 · scoring model v2023.03.01
26 Dec 20240.12997 · crossed 0.10
17 Mar 20250.0373 · crossed 0.10 · scoring model v2025.03.14
29 Mar 20250.21084 · crossed 0.10
30 Mar 20250.06312 · crossed 0.10
6 Sep 20250.109 · crossed 0.10
18 Nov 20250.08217 · crossed 0.10
21 Nov 20250.109 · crossed 0.10
15 Jun 20260.04369 · crossed 0.10 · scoring model v2026.06.15
11 Jul 20260.04716

This score more than doubled inside 72 hours. Both observations are in the full history below.

Show all 49 observations
14 Apr 20210.13741
6 Jan 20220.41682
4 Feb 20220.3168
1 Apr 20220.04475
4 May 20220.04844
7 Mar 20230.00946
31 Mar 20230.02734
14 Apr 20230.01068
27 Apr 20230.02414
11 May 20230.02118
23 May 20230.02358
19 Jun 20230.01481
2 Jul 20230.01728
12 Aug 20230.01394
8 Sep 20230.01357
22 Sep 20230.01432
19 Nov 20230.01684
3 Dec 20230.01304
1 Jan 20240.02373
3 Jan 20240.02172
2 Feb 20240.02421
19 Feb 20240.01825
7 Apr 20240.01295
18 Jul 20240.01567
5 Aug 20240.01599
20 Aug 20240.03260
6 Sep 20240.01915
22 Sep 20240.01964
9 Oct 20240.01822
23 Oct 20240.01292
25 Nov 20240.01305
11 Dec 20240.01811
17 Dec 20240.09615
26 Dec 20240.12997
25 Jan 20250.17298
9 Feb 20250.12997
17 Mar 20250.0373
19 Mar 20250.04602
28 Mar 20250.04749
29 Mar 20250.21084
30 Mar 20250.06312
16 Apr 20250.05217
16 Jul 20250.09107
6 Sep 20250.109
18 Nov 20250.08217
21 Nov 20250.109
18 Mar 20260.10589
15 Jun 20260.04369
11 Jul 20260.04716

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.04716Published2020-10-16Index as of2026-07-11

Exploit probability more than doubled between 2025-03-28 and 2025-03-29 (0.04749 → 0.21084) and the record had been public for 5 years, 8 months when this index was last written.

Published 2020-10-16 receipt · Index as of 2026-07-11 derived

The pattern, elsewhere

This record is one instance of CWE-20, improper input validation. The index holds 13347 prior instances of this class, 73 KEV-listed. The nearest of its KEV-listed records are drawn beside this. [email protected]

CVE-2024-30040 · Microsoft Windows 10 Version 1809matches 8 of 10KEV listed · 2024receipt
CVE-2019-0604 · Microsoft SharePoint Servermatches 7 of 10KEV listed · 2019receipt
CVE-2025-32706 · Microsoft Windows 10 Version 1507matches 7 of 10KEV listed · 2025receipt
CVE-2024-21413 · Microsoft 365 Apps for Enterprisematches 7 of 10KEV listed · 2024receipt
CVE-2022-47966matches 6 of 9KEV listed · 2023receipt
CVE-2022-29499matches 6 of 9KEV listed · 2022receipt

"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

13347 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

Its defect family

microsoft windows

Of the 24 records in this family, this is the only one whose title names microsoft graphics components.

Grouped by shared product and weakness, not by shared vulnerability. Each record's own state is on its own page.

Family membership: computed, pro@dim2000

This record is one of a group, and the group's page describes all of them. This page is kept and dated, and the defect family's own page is the one we offer for indexing: the whole group.

Browse the index from here

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

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.