vciy

CVE-2024-26169

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 Error Reporting Service Elevation of Privilege Vulnerability

CVE-2024-261694 of 4 sources documented this
76

rank 76 = 40 + 20 + 1 + 9 + 6

rank@v1 · act now

Someone is already using it

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

EPSS 0.04014 · CISA KEV listed  ·  without this subject the record ranks 36

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 7.8, from the CNA  ·  without this subject the record ranks 56

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

rose on 2025-10-29  ·  without this subject the record ranks 75

How much of the world it touches

NVD CPE configurations

13 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 70

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

$200,000 = $4.99M incident cost x 1 exposure x 0.04014 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.04014EPSSKEV · LISTED
Severity7.8 HIGHreceipt
Harmtotal loss · ransomware-linkedreceipt
Exploitationransomware use knownreceipt
Defensefix version namedreceipt
Movementthreshold crossedreceipt
RISING10Risen from 0.00043 to 0.04014 across 48 observations. arc-rules@v1

Foresight · where to check next

Microsoft WindowsMicrosoft WindowsMicrosoft WindowsCVE-2002-036726169

This record is one instance of CWE-269, improper privilege management. The index holds 3613 prior instances of this class, 20 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 1809? 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-269 Improper Privilege Managementreceipt
Published consequencesCWE-269: Access Control: Gain Privileges or Assume Identity[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 in10.0.17763.5576; 10.0.20348.2340; 10.0.22000.2836; 10.0.19044.4170; 10.0.22621.3296; 10.0.19045.4170; 10.0.22631.3296; 10.0.25398.763; 10.0.10240.20526…receipt
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 2024-07-04receipt
CISA required actionApply updates per vendor instructions or discontinue use of the product if updates are unavailable.receipt
Published to CISA KEV93 daysderived

Exploit Status & Known PoCs a ladder, not a score

Current rung: Ransomware campaign use known, 2024-06-13.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published · 1 public repository2025-11-17receipt
  • RUNG 3Exploited in the wild · CISA KEV listed2024-06-13receipt
  • RUNG 4Ransomware campaign use known2024-06-13receipt

Authority who says so

CVSS, the CNA7.8 HIGHreceipt
Exploit probability0.04014 · top 10% of all CVEsreceipt
Blast breadth2 products across 1 vendorderived
Assigned bymicrosoftreceipt
Recorded changes62 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productMicrosoft Windows 10 Version 1809; Microsoft Windows Server 2019; Microsoft Windows Server 2019 (Server Core installation); Microsoft Windows Server 2022; Microsoft Windows 11 version 21H2…receipt
Published rangesmicrosoft windows 10 1507 < 10.0.10240.20526; microsoft windows 10 1607 < 10.0.14393.6796; microsoft windows 10 1809 < 10.0.17763.5576; microsoft windows 10 21h2 < 10.0.19044.4170receipt
Show all 13 published ranges
microsoft windows 10 1507 < 10.0.10240.20526
microsoft windows 10 1607 < 10.0.14393.6796
microsoft windows 10 1809 < 10.0.17763.5576
microsoft windows 10 21h2 < 10.0.19044.4170
microsoft windows 10 22h2 < 10.0.19045.4170
microsoft windows 11 21h2 < 10.0.22000.2836
microsoft windows 11 22h2 < 10.0.22621.3296
microsoft windows 11 23h2 < 10.0.22631.3296
microsoft windows server 2008 r2
microsoft windows server 2012 r2
microsoft windows server 2019 < 10.0.17763.5576
microsoft windows server 2022 < 10.0.20348.2333
microsoft windows server 2022 23h2 < 10.0.25398.763
Fixed in10.0.17763.5576; 10.0.20348.2340; 10.0.22000.2836; 10.0.19044.4170; 10.0.22621.3296; 10.0.19045.4170; 10.0.22631.3296; 10.0.25398.763; 10.0.10240.20526…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.

Attack path

Local accessrequires low privilegesCISA KEV listingadded 06-13 · due 07-04Microsoft Windows Server 2019CWE-269 improper privilege manage…Full compromise (C/I/A)C:H / I:H / A:Hmandates remediationexploits CWE-269data compromise

What it is stated by the CNA

Windows Error Reporting Service Elevation of Privilege Vulnerability receipt

NVD's analysis a second authority

weakness
CWE-269
affected versions
microsoft windows 10 1507 < 10.0.10240.20526; microsoft windows 10 1607 < 10.0.14393.6796; microsoft windows 10 1809 < 10.0.17763.5576; and 10 more, listed in full below
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

2024-06-13Added to CISA KEV2024-07-04CISA remediation due2025-03-08EPSS moved 0.02 to 0.122026-06-15EPSS moved 0.35 to 0.04

Movement the material steps

13 Mar 20240.00043
8 Mar 20250.11866 · crossed 0.10
17 Mar 20250.35826 · scoring model v2025.03.14
20 Apr 20250.47903
15 May 20250.28449
15 Jun 20260.04014 · crossed 0.10 · scoring model v2026.06.15
Show all 48 observations
13 Mar 20240.00043
14 Jun 20240.00146
15 Jun 20240.00078
19 Jun 20240.00059
30 Jul 20240.00316
15 Aug 20240.00052
17 Dec 20240.00670
30 Jan 20250.00786
10 Feb 20250.00918
22 Feb 20250.01693
8 Mar 20250.11866
17 Mar 20250.35826
19 Mar 20250.32482
20 Mar 20250.33668
27 Mar 20250.32482
28 Mar 20250.33668
29 Mar 20250.32482
30 Mar 20250.33668
15 Apr 20250.42737
20 Apr 20250.47903
26 Apr 20250.42172
1 May 20250.38915
15 May 20250.28449
28 May 20250.31387
31 May 20250.30848
1 Jul 20250.26389
25 Jul 20250.27935
1 Aug 20250.26205
23 Aug 20250.26702
4 Sep 20250.29237
5 Sep 20250.28716
16 Sep 20250.22048
2 Oct 20250.21607
17 Oct 20250.23879
22 Oct 20250.24004
24 Oct 20250.24476
29 Oct 20250.32028
6 Nov 20250.31483
14 Nov 20250.34581
18 Nov 20250.29283
21 Nov 20250.34581
18 Feb 20260.35146
6 Mar 20260.34581
21 Mar 20260.35146
1 Apr 20260.34581
23 May 20260.35146
5 Jun 20260.34581
15 Jun 20260.04014

48 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.04014Published2024-03-12CISA KEV2024-06-13Public PoC2025-11-17Index as of2026-09-04

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

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

Published 2024-03-12 receipt · CISA KEV 2024-06-13 receipt · Public PoC 2025-11-17 receipt · Index as of 2026-09-04 derived

The pattern, elsewhere

This record is one instance of CWE-269, improper privilege management. The index holds 3613 prior instances of this class, 20 KEV-listed. The nearest of its KEV-listed records are drawn beside this. [email protected]

CVE-2019-1215 · Microsoft Windowsmatches 9 of 9KEV listed · 2019receipt
CVE-2019-1388 · Microsoft Windowsmatches 9 of 9KEV listed · 2019receipt
CVE-2019-1405 · Microsoft Windowsmatches 9 of 9KEV listed · 2019receipt
CVE-2026-21533 · Microsoft Windows 10 Version 1607matches 9 of 9KEV listed · 2026receipt
CVE-2024-38014 · Microsoft Windows 10 Version 1507matches 9 of 9KEV listed · 2024receipt
CVE-2002-0367matches 8 of 8KEV listed · 2003receipt

"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

3613 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

Browse the index from here

These are index-wide views, not findings about CVE-2024-26169.

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.