vciy

CVE-2019-1344

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 information disclosure vulnerability exists in the way that the Windows Code Integrity Module handles objects in memory, aka 'Windows Code…

CVE-2019-13444 of 4 sources documented this
23

rank 23 = 1 + 14 + 0 + 8 + 0

rank@v1 · backlog

Someone is already using it

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

EPSS 0.03067  ·  without this subject the record ranks 22

What it costs you if it fires

NVD CVSS base score, then the CNA's own

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

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 23

How much of the world it touches

NVD CPE configurations

10 products in the CPE ranges  ·  without this subject the record ranks 15

Someone else already set the date

CISA KEV remediation due date

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

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$93,700over the next 30 days, if this record is yours
Movement-$430,000on 2025-03-30, the last material move, 1 year, 4 months before this reading
Basisassumeda published average, not your estate

$93,700 = $4.99M incident cost x 0.6121449559255632 exposure x 0.03067 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.03067EPSSNOT IN KEVas of 2026-09-20
Severity5.5 MEDIUMreceipt
Harmpartial impactreceipt
Exploitationnone in held sources
Defenseno fix version held
Movementdoubled within 72hreceipt
PLATEAU10Minimal movement since 2025-03-30, 489 days at 0.03, as of 2026-08-01. arc-rules@v1

Foresight · where to check next

Apple macOSMicrosoft WindowsLinuxMicrosoft WindowsCVE-2014-0160polkit1344

This record is one instance of CWE-125, out-of-bounds read. The index holds 9767 prior instances of this class, 19 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? 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 lossreceipt
Scored fromCVSS v3.1 · NVD's vectorreceipt
Weakness classCWE-125 Out-of-bounds Readreceipt
Published consequencesCWE-125: Confidentiality: Read Memory; Confidentiality: Bypass Protection Mechanism; Availability: DoS: Crash, Exit, or Restart; Other: Varies by Context[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 1 Aug 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, NVD5.5 MEDIUMreceipt
Exploit probability0.03067 · top 13% of all CVEsreceipt
Blast breadth2 products across 1 vendorderived
Assigned bymicrosoftreceipt
Recorded changes17 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productMicrosoft Windows; Microsoft Windows Server; Microsoft Windows 10 Version 1903 for 32-bit Systems; Microsoft Windows 10 Version 1903 for x64-based Systems…receipt
Published rangesmicrosoft windows 10 1607; microsoft windows 10 1703; microsoft windows 10 1709; microsoft windows 10 1803receipt
Show all 10 published ranges
microsoft windows 10 1607
microsoft windows 10 1703
microsoft windows 10 1709
microsoft windows 10 1803
microsoft windows 10 1809
microsoft windows 10 1903
microsoft windows server 2008 r2
microsoft windows server 2012 r2
microsoft windows server 2016 1803
microsoft windows server 2016 1903

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 information disclosure vulnerability exists in the way that the Windows Code Integrity Module handles objects in memory, aka 'Windows Code Integrity Module Information Disclosure Vulnerability'. receipt

NVD's analysis a second authority

severity
5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
weakness
CWE-125
affected versions
microsoft windows 10 1607; microsoft windows 10 1703; microsoft windows 10 1709; and 7 more, listed in full below

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

Dated events

2022-02-04EPSS moved 0.24 to 0.022025-03-30EPSS moved 0.21 to 0.07

Movement the material steps

14 Apr 20210.24372
4 Feb 20220.01909 · crossed 0.10
7 Mar 20234.2e-4 · scoring model v2023.03.01
17 Mar 20250.09028 · scoring model v2025.03.14
29 Mar 20250.21089 · crossed 0.10
30 Mar 20250.0701 · crossed 0.10
15 Jun 20260.02863 · scoring model v2026.06.15
1 Aug 20260.03067

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

Show all 17 observations
14 Apr 20210.24372
4 Feb 20220.01909
7 Mar 20234.2e-4
8 Mar 20230.00042
16 Sep 20230.00055
3 Oct 20230.00043
8 Feb 20250.00060
17 Mar 20250.09028
19 Mar 20250.0701
29 Mar 20250.21089
30 Mar 20250.0701
17 Apr 20250.08119
23 Oct 20250.05455
18 Nov 20250.01721
21 Nov 20250.05455
15 Jun 20260.02863
1 Aug 20260.03067

17 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.03067Published2019-10-10Index as of2026-08-01

Exploit probability more than doubled between 2025-11-18 and 2025-11-21 (0.01721 → 0.05455) and the record had been public for 6 years, 9 months when this index was last written.

Published 2019-10-10 receipt · Index as of 2026-08-01 derived

The pattern, elsewhere

This record is one instance of CWE-125, out-of-bounds read. The index holds 9767 prior instances of this class, 19 KEV-listed. The nearest of its KEV-listed records are drawn beside this. [email protected]

CVE-2022-22674 · Apple macOSmatches 8 of 9KEV listed · 2022receipt
CVE-2025-24991 · Microsoft Windows 10 Version 1507matches 7 of 9KEV listed · 2025receipt
CVE-2024-53150 · Linuxmatches 7 of 9KEV listed · 2024receipt
CVE-2023-36424 · Microsoft Windows 11 version 22H3matches 7 of 9KEV listed · 2023receipt
CVE-2014-0160matches 6 of 8KEV listed · 2014receipt
CVE-2021-4034 · polkitmatches 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

9767 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

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

Nothing we hold separates this record from the others in its defect family. 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-1344.

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.