vciy

CVE-2019-1064

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.

Windows Elevation of Privilege Vulnerability

CVE-2019-10643 of 4 sources documented this
66

rank 66 = 40 + 20 + 0 + 0 + 6

rank@v1 · this cycle

Someone is already using it

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

EPSS 0.06886 · CISA KEV listed  ·  without this subject the record ranks 26

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 7.8, 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 66

How much of the world it touches

NVD CPE configurations

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

Someone else already set the date

CISA KEV remediation due date

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

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

$344,000 = $4.99M incident cost x 1 exposure x 0.06886 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.06886EPSSKEV · LISTED
Severity7.8 HIGHreceipt
Harmtotal loss · ransomware-linkedreceipt
Exploitationransomware use knownreceipt
Defenseno fix version held
Movementthreshold crossedreceipt
PLATEAU10Minimal movement since 2025-03-17, 536 days at 0.07, as of 2026-09-04. arc-rules@v1

Foresight · where to check next

Microsoft WindowsMicrosoft WindowsMicrosoft WindowsMicrosoft Windows1064

This record is one instance of CWE-59, improper link resolution before file access ('link following'). The index holds 1732 prior instances of this class, 24 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 1703? 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 · low attack complexityreceipt
ImpactComplete confidentiality, integrity and availability lossreceipt
Scored fromCVSS v3.1 · the CNA's vectorreceipt
Weakness classCWE-59 Improper Link Resolution Before File Access ('Link Following')receipt
Published consequencesCWE-59: Confidentiality, Integrity, Access Control: Read Files or Directories, Modify Files or Directories, Bypass Protection Mechanism; Other: Execute Unauthorized Code or Commands[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-04-05receipt
CISA required actionApply updates per vendor instructions.receipt
Published to CISA KEV1007 daysderived

Exploit Status & Known PoCs a ladder, not a score

Current rung: Ransomware campaign use known, 2022-03-15.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published · 3 public repositories2019-06-12receipt
  • RUNG 3Exploited in the wild · CISA KEV listed2022-03-15receipt
  • RUNG 4Ransomware campaign use known2022-03-15receipt

Authority who says so

CVSS, the CNA7.8 HIGHreceipt
CVSS, NVD7.8 HIGHreceipt
Exploit probability0.06886 · top 6% of all CVEsreceipt
Assigned bymicrosoftreceipt
Recorded changes58 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productMicrosoft Windows 10 Version 1703; Microsoft Windows 10 Version 1803; Microsoft Windows Server, version 1803 (Server Core Installation); Microsoft Windows 10 Version 1809…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

An elevation of privilege vulnerability exists when Windows AppX Deployment Service (AppXSVC) improperly handles hard links. An attacker who successfully exploited this vulnerability could run processes in an elevated context. An attacker could then install programs; view, change or delete data. 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 security update addresses the vulnerability by correcting how Windows AppX Deployment Service handles hard links. receipt

NVD's analysis a second authority

severity
7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
weakness
CWE-59
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

check it yourself msrc.microsoft.com receipt

Dated events

2022-02-04EPSS moved 0.18 to 0.012022-03-15Added to CISA KEV2022-04-05CISA remediation due2023-03-07EPSS moved 0.02 to 0.932026-06-15EPSS moved 0.12 to 0.07

Movement the material steps

14 Apr 20210.17642
4 Feb 20220.01372 · crossed 0.10
7 Mar 20230.93434 · crossed 0.10 and 0.50 and 0.90 · scoring model v2023.03.01
24 Oct 20230.88811 · crossed 0.90
29 Jan 20250.77626
17 Mar 20250.09557 · crossed 0.10 and 0.50 · scoring model v2025.03.14
19 Mar 20250.12775 · crossed 0.10
20 Mar 20250.09557 · crossed 0.10
25 Mar 20250.11997 · crossed 0.10
18 Nov 20250.08461 · crossed 0.10
21 Nov 20250.11342 · crossed 0.10
15 Jun 20260.06886 · crossed 0.10 · scoring model v2026.06.15
Show all 44 observations
14 Apr 20210.17642
4 Feb 20220.01372
21 May 20220.01641
7 Mar 20230.93434
14 Mar 20230.93588
19 May 20230.93500
19 Jun 20230.93652
22 Jul 20230.92134
22 Aug 20230.90669
24 Oct 20230.88811
6 Jan 20240.87880
7 Feb 20240.88076
12 Mar 20240.87481
17 Apr 20240.87735
23 Jun 20240.87930
29 Jul 20240.88404
20 Sep 20240.85948
23 Nov 20240.81786
29 Jan 20250.77626
25 Feb 20250.68949
17 Mar 20250.09557
19 Mar 20250.12775
20 Mar 20250.09557
25 Mar 20250.11997
27 Mar 20250.12856
28 Mar 20250.11997
29 Mar 20250.12856
30 Mar 20250.11997
5 Apr 20250.13869
14 Apr 20250.11558
21 May 20250.14517
15 Jun 20250.15538
14 Jul 20250.13514
28 Sep 20250.13668
16 Oct 20250.1645
22 Oct 20250.1641
23 Oct 20250.16622
30 Oct 20250.11869
18 Nov 20250.08461
21 Nov 20250.11342
17 Mar 20260.1242
28 Mar 20260.12218
13 May 20260.11822
15 Jun 20260.06886

44 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.06886Published · Public PoC2019-06-12CISA KEV2022-03-15Index as of2026-09-04

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

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

Published 2019-06-12 receipt · Public PoC 2019-06-12 receipt · CISA KEV 2022-03-15 receipt · Index as of 2026-09-04 derived

The pattern, elsewhere

This record is one instance of CWE-59, improper link resolution before file access ('link following'). The index holds 1732 prior instances of this class, 24 KEV-listed. The nearest of its KEV-listed records are drawn beside this. [email protected]

CVE-2025-60710 · Microsoft Windows 11 Version 24H2matches 9 of 9KEV listed · 2025receipt
CVE-2022-21999 · Microsoft Windows 10 Version 1809matches 9 of 9KEV listed · 2022receipt
CVE-2020-0638 · Microsoft Windowsmatches 9 of 9KEV listed · 2020receipt
CVE-2019-0841 · Microsoft Windowsmatches 9 of 9KEV listed · 2019receipt
CVE-2019-1069 · Microsoft Windows 10 Version 1703matches 9 of 9KEV listed · 2019receipt
CVE-2019-1129 · Microsoft Windowsmatches 9 of 9KEV listed · 2019receipt

"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

1732 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 holding a CISA KEV listing: Microsoft Windows AppX Deployment Service (AppXSVC) Privileg.

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-2019-1064.

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.