vciy

CVE-2020-1054

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.

Win32k Elevation of Privilege Vulnerability

CVE-2020-10544 of 4 sources documented this
69

rank 69 = 40 + 18 + 1 + 4 + 6

rank@v1 · this cycle

Someone is already using it

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

EPSS 0.54158 · CISA KEV listed  ·  without this subject the record ranks 29

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 7.0, from NVD  ·  without this subject the record ranks 51

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

rose on 2025-10-22  ·  without this subject the record ranks 68

How much of the world it touches

NVD CPE configurations

2 products in the CPE ranges  ·  without this subject the record ranks 65

Someone else already set the date

CISA KEV remediation due date

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

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$2.70Mover the next 30 days, if this record is yours
Movement-$3.06Mon 2022-02-04, the last material move, 4 years, 7 months before this reading
Basisassumeda published average, not your estate

$2.70M = $4.99M incident cost x 1 exposure x 0.54158 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.54158EPSSKEV · LISTED
Severity7 HIGHreceipt
Harmtotal lossreceipt
Exploitationin the wild · KEVreceipt
Defenseno fix version held
Movementdoubled within 72hreceipt
PLATEAU10Minimal movement since 2026-06-15, 81 days at 0.54, as of 2026-09-04. arc-rules@v1

Foresight · where to check next

Microsoft WindowsMicrosoft Windows1054

This record is one instance of CWE-787, out-of-bounds write. The index holds 14893 prior instances of this class, 164 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 1507? 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 · low privileges required · no user interaction · high attack complexityreceipt
ImpactComplete confidentiality, integrity and availability lossreceipt
Scored fromCVSS v3.1 · the CNA's vectorreceipt
Weakness classCWE-787 Out-of-bounds Writereceipt
Published consequencesCWE-787: Integrity: Modify Memory, Execute Unauthorized Code or Commands; Availability: DoS: Crash, Exit, or Restart; Other: Unexpected State[email protected]
Ransomware campaign useUnknown to CISAreceipt

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-05-03receipt
CISA required actionApply updates per vendor instructions.receipt
Published to CISA KEV531 daysderived

Exploit Status & Known PoCs a ladder, not a score

Current rung: Exploited in the wild · CISA KEV listed, 2021-11-03.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published · 4 public repositories2020-06-16receipt
  • RUNG 3Exploited in the wild · CISA KEV listed2021-11-03receipt
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, the CNA7 HIGHreceipt
CVSS, NVD7 HIGHreceipt
Exploit probability0.54158 · top 1% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned bymicrosoftreceipt
Recorded changes80 · last 18 Sep 2026derived

Affected & Fixed Versions as published

Affected productMicrosoft Windows 10 Version 1507; Microsoft Windows 10 Version 1607; Microsoft Windows 10 Version 1709; Microsoft Windows 10 Version 1709 for 32-bit Systems; Microsoft Windows 10 Version 1803…receipt
Published rangesmicrosoft windows server 2008 r2; microsoft windows server 2012 r2receipt

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

An elevation of privilege vulnerability exists in Windows when the Windows kernel-mode driver fails to properly handle objects in memory. An attacker who successfully exploited this vulnerability could run arbitrary code in kernel mode. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. To exploit this vulnerability, an attacker would first have to log on to the system. An attacker could then run a specially crafted application that could exploit the vulnerability and take control of an affected system. The update addresses this vulnerability by correcting how the Windows kernel-mode driver handles objects in memory. receipt

NVD's analysis a second authority

severity
7 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
weakness
CWE-787
affected versions
microsoft windows server 2008 r2; microsoft windows server 2012 r2
also scored by
[email protected] 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H · 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

check it yourself msrc.microsoft.com receipt

Dated events

2021-09-14EPSS moved 0.70 to 0.242021-11-03Added to CISA KEV2022-05-03CISA remediation due2025-03-17EPSS moved 0.01 to 0.752026-06-15EPSS moved 0.81 to 0.53

Movement the material steps

14 Apr 20210.70425
14 Sep 20210.24372 · crossed 0.50
16 Sep 20210.70425 · crossed 0.50
4 Feb 20220.09099 · crossed 0.10 and 0.50
7 Mar 20230.00204 · scoring model v2023.03.01
17 Mar 20250.74594 · crossed 0.10 and 0.50 · scoring model v2025.03.14
18 Nov 20250.51031
21 Nov 20250.80404
15 Jun 20260.52778 · scoring model v2026.06.15
20 Aug 20260.54158

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

Show all 66 observations
14 Apr 20210.70425
14 Sep 20210.24372
16 Sep 20210.70425
4 Feb 20220.09099
7 Mar 20230.00204
17 Mar 20230.00250
13 Apr 20230.00252
8 May 20230.00179
10 May 20230.00182
25 May 20230.00259
24 Jun 20230.00266
7 Sep 20230.00196
24 Sep 20230.00209
9 Oct 20230.00198
25 Oct 20230.00232
11 Nov 20230.00222
21 Feb 20240.00228
25 Mar 20240.00465
27 Apr 20240.00454
14 May 20240.00341
28 May 20240.00438
14 Jun 20240.00427
30 Jun 20240.00574
16 Jul 20240.01029
2 Oct 20240.00801
1 Nov 20240.01108
17 Nov 20240.01453
17 Dec 20240.01361
16 Jan 20250.01209
17 Mar 20250.74594
19 Mar 20250.72819
20 Mar 20250.76297
22 Mar 20250.76997
23 Mar 20250.80387
27 Mar 20250.79201
28 Mar 20250.80387
29 Mar 20250.79201
30 Mar 20250.80387
15 Apr 20250.80651
26 Apr 20250.80387
15 May 20250.80314
30 May 20250.80387
23 Jul 20250.80651
26 Jul 20250.77317
5 Aug 20250.76997
1 Sep 20250.76297
12 Sep 20250.74062
1 Oct 20250.75455
22 Oct 20250.80404
27 Oct 20250.81228
28 Oct 20250.80404
18 Nov 20250.51031
21 Nov 20250.80404
8 Dec 20250.82335
27 Dec 20250.83052
28 Dec 20250.82335
23 Feb 20260.80933
20 Apr 20260.81584
21 Apr 20260.81826
25 Apr 20260.81584
14 May 20260.824
25 May 20260.81207
30 May 20260.81456
12 Jun 20260.81207
15 Jun 20260.52778
20 Aug 20260.54158

66 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.54158Published2020-05-21Public PoC2020-06-16CISA KEV2021-11-03Index as of2026-09-04

Listed by CISA 531 days after it published, exploit probability more than doubled between 2021-09-14 and 2021-09-16 (0.24372 → 0.70425) and the record had been public for 6 years, 3 months when this index was last written.

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

Published 2020-05-21 receipt · Public PoC 2020-06-16 receipt · CISA KEV 2021-11-03 receipt · Index as of 2026-09-04 derived

The pattern, elsewhere

This record is one instance of CWE-787, out-of-bounds write. The index holds 14893 prior instances of this class, 164 KEV-listed. The nearest of its KEV-listed records are drawn beside this. [email protected]

CVE-2022-21882 · Microsoft Windows 10 Version 1809matches 9 of 9KEV listed · 2022receipt
CVE-2024-30051 · Microsoft Windows 10 Version 1809matches 8 of 9KEV listed · 2024receipt
CVE-2023-23376 · Microsoft Windows 10 Version 1507matches 8 of 9KEV listed · 2023receipt
CVE-2023-28252 · Microsoft Windows 10 Version 1809matches 8 of 9KEV listed · 2023receipt
CVE-2022-24521 · Microsoft Windows 10 Version 1809matches 8 of 9KEV listed · 2022receipt
CVE-2022-37969 · Microsoft Windows 10 Version 1809matches 8 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

14893 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 10 version 1507

Of the 9 records in this family, this is the only one holding a CISA KEV listing: Microsoft Win32k Privilege Escalation Vulnerability.

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

Family membership: held values

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

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.