vciy

CVE-2019-0697

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.

A memory corruption vulnerability exists in the Windows DHCP client when an attacker sends specially crafted DHCP responses to a client, aka 'Windows…

CVE-2019-06974 of 4 sources documented this
38

rank 38 = 8 + 25 + 0 + 5 + 0

rank@v1 · scheduled

Someone is already using it

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

EPSS 0.32915  ·  without this subject the record ranks 30

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 9.8, from NVD  ·  without this subject the record ranks 13

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 38

How much of the world it touches

NVD CPE configurations

3 products in the CPE ranges  ·  without this subject the record ranks 33

Someone else already set the date

CISA KEV remediation due date

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

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

$1.64M = $4.99M incident cost x 1 exposure x 0.32915 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.32915EPSSNOT IN KEVas of 2026-09-20
Severity9.8 CRITICALreceipt
Harmtotal loss · unauthenticatedreceipt
Exploitationnone in held sources
Defenseno fix version held
Movementrisenreceipt
PLATEAU10Minimal movement since 2025-12-10, 270 days at 0.33, as of 2026-09-06. arc-rules@v1

Foresight · where to check next

FortinetFortinetSonicWall SMA100Microsoft WindowsMicrosoft Windows0697

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

Reachnetwork-reachable · no privileges required · no user interaction · low attack complexityreceipt
ImpactComplete confidentiality, integrity and availability lossreceipt
Scored fromCVSS v3.0 · NVD'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]

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

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, NVD9.8 CRITICALreceipt
Exploit probability0.32915 · top 2% of all CVEsreceipt
Blast breadth2 products across 1 vendorderived
Assigned bymicrosoftreceipt
Recorded changes33 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productMicrosoft Windows; Microsoft Windows Serverreceipt
Published rangesmicrosoft windows 10 1803; microsoft windows 10 1809; microsoft windows server 2016 1803receipt

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

A memory corruption vulnerability exists in the Windows DHCP client when an attacker sends specially crafted DHCP responses to a client, aka 'Windows DHCP Client Remote Code Execution Vulnerability'. This CVE ID is unique from CVE-2019-0698, CVE-2019-0726. receipt

NVD's analysis a second authority

severity
9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
weakness
CWE-787
affected versions
microsoft windows 10 1803; microsoft windows 10 1809; microsoft windows server 2016 1803

check it yourself portal.msrc.microsoft.com receipt

Dated events

2022-01-06EPSS moved 0.08 to 0.282023-03-07EPSS moved 0.21 to 0.912025-12-10EPSS moved 0.46 to 0.30

Movement the material steps

14 Apr 20210.07953
6 Jan 20220.27938 · crossed 0.10
1 Apr 20220.12157
7 Mar 20230.90833 · crossed 0.50 and 0.90 · scoring model v2023.03.01
1 Apr 20230.89193 · crossed 0.90
18 May 20230.90391 · crossed 0.90
17 Jul 20240.88925 · crossed 0.90
25 Nov 20240.76115
22 Dec 20240.63786
15 Feb 20250.48561 · crossed 0.50
17 Mar 20250.56416 · crossed 0.50 · scoring model v2025.03.14
24 May 20250.46058 · crossed 0.50
18 Nov 20250.56647 · crossed 0.50
21 Nov 20250.46058 · crossed 0.50
10 Dec 20250.30454
15 Jun 20260.29648 · scoring model v2026.06.15
6 Sep 20260.32915
Show all 33 observations
14 Apr 20210.07953
6 Jan 20220.27938
4 Feb 20220.3686
17 Mar 20220.34454
1 Apr 20220.12157
3 Oct 20220.15261
13 Jan 20230.16608
19 Feb 20230.20741
7 Mar 20230.90833
1 Apr 20230.89193
18 May 20230.90391
20 Aug 20230.90175
17 Jul 20240.88925
19 Sep 20240.83629
25 Nov 20240.76115
17 Dec 20240.75582
22 Dec 20240.63786
21 Jan 20250.66592
15 Feb 20250.48561
17 Mar 20250.56416
19 Mar 20250.50095
29 Mar 20250.59129
30 Mar 20250.50095
24 May 20250.46058
18 Nov 20250.56647
21 Nov 20250.46058
10 Dec 20250.30454
15 Jun 20260.29648
22 Aug 20260.32915
23 Aug 20260.31581
30 Aug 20260.32915
5 Sep 20260.31581
6 Sep 20260.32915

33 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.32915Published2019-04-08Index as of2026-09-06

The record had been public for 7 years, 4 months when this index was last written.

Published 2019-04-08 receipt · Index as of 2026-09-06 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-2024-21762 · Fortinet FortiProxymatches 8 of 9KEV listed · 2024receipt
CVE-2022-42475 · Fortinet FortiProxymatches 8 of 9KEV listed · 2023receipt
CVE-2023-27997 · Fortinet FortiOS-6K7Kmatches 8 of 9KEV listed · 2023receipt
CVE-2021-20038 · SonicWall SMA100matches 8 of 9KEV listed · 2021receipt
CVE-2024-30051 · Microsoft Windows 10 Version 1809matches 7 of 9KEV listed · 2024receipt
CVE-2023-23376 · Microsoft Windows 10 Version 1507matches 7 of 9KEV listed · 2023receipt

"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

Browse the index from here

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

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.