vciy

CVE-2019-0803

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.

An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in memory, aka 'Win32k Elevation…

CVE-2019-08034 of 4 sources documented this
71

rank 71 = 40 + 20 + 1 + 4 + 6

rank@v1 · act now

Someone is already using it

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

EPSS 0.44954 · 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 7.8, 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 70

How much of the world it touches

NVD CPE configurations

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

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$2.24Mover the next 30 days, if this record is yours
Movement-$23,700on 2026-03-10, the last material move, 6 months before this reading
Basisassumeda published average, not your estate

$2.24M = $4.99M incident cost x 1 exposure x 0.44954 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.44954EPSSKEV · LISTED
Severity7.8 HIGHreceipt
Harmtotal loss · ransomware-linkedreceipt
Exploitationransomware use knownreceipt
Defenseno fix version held
Movementrisenreceipt
PLATEAU10Minimal movement since 2026-06-15, 94 days at 0.45, as of 2026-09-17. arc-rules@v1

Foresight · where to check next

No weakness class or product neighbourhood is held for this record, so this index cannot name anywhere to check next. That is an absence in the record, not a finding about the software.

Color is a claim, not decoration:the hostile worldthe defenseno signal

Running Microsoft Windows? 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 · NVD's vectorreceipt
Weakness classNo CWE mapping in held sources.
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 17 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 KEV939 daysderived

Exploit Status & Known PoCs a ladder, not a score

Current rung: Ransomware campaign use known, 2021-11-03.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published · 2 public repositories2019-05-17receipt
  • RUNG 3Exploited in the wild · CISA KEV listed2021-11-03receipt
  • RUNG 4Ransomware campaign use known2021-11-03receipt

Authority who says so

CVSS, NVD7.8 HIGHreceipt
Exploit probability0.44954 · top 1% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned bymicrosoftreceipt
Recorded changes45 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productMicrosoft Windows; Microsoft Windows Serverreceipt
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 Win32k component fails to properly handle objects in memory, aka 'Win32k Elevation of Privilege Vulnerability'. This CVE ID is unique from CVE-2019-0685, CVE-2019-0859. 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
affected versions
microsoft windows server 2008 r2; microsoft windows server 2012 r2
also scored by
7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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

Dated events

2021-11-03Added to CISA KEV2022-02-04EPSS moved 0.24 to 0.022022-05-03CISA remediation due2025-03-17EPSS moved 0.01 to 0.852026-06-15EPSS moved 0.89 to 0.45

Movement the material steps

14 Apr 20210.24372
4 Feb 20220.01909 · crossed 0.10
7 Mar 20235e-4 · scoring model v2023.03.01
17 Mar 20250.84886 · crossed 0.10 and 0.50 · scoring model v2025.03.14
18 Nov 20250.6833
21 Nov 20250.87316
5 Jan 20260.90359 · crossed 0.90
10 Mar 20260.89827 · crossed 0.90
15 Jun 20260.4523 · crossed 0.50 · scoring model v2026.06.15
17 Sep 20260.44954
Show all 31 observations
14 Apr 20210.24372
4 Feb 20220.01909
7 Mar 20235e-4
8 Mar 20230.00050
21 Mar 20230.00476
5 Jul 20230.00387
3 Aug 20230.00445
5 Sep 20230.00527
13 Jun 20240.00615
8 Aug 20240.00534
30 Aug 20240.00448
26 Nov 20240.00569
17 Dec 20240.01126
22 Jan 20250.01151
17 Mar 20250.84886
17 Aug 20250.8507
30 Aug 20250.84886
15 Sep 20250.82877
25 Sep 20250.78606
17 Oct 20250.80049
22 Oct 20250.86813
30 Oct 20250.87316
18 Nov 20250.6833
21 Nov 20250.87316
18 Dec 20250.86574
5 Jan 20260.90359
23 Jan 20260.90302
10 Mar 20260.89827
20 May 20260.8884
15 Jun 20260.4523
17 Sep 20260.44954

31 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.44954Published2019-04-09Public PoC2019-05-17CISA KEV2021-11-03Index as of2026-09-17

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

Published 2019-04-09 receipt · Public PoC 2019-05-17 receipt · CISA KEV 2021-11-03 receipt · Index as of 2026-09-17 derived

Siblings and hubs

Records related to this one

Browse the index from here

These are index-wide views, not findings about CVE-2019-0803.

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.