vciy

CVE-2023-4069

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.

Type Confusion in V8 in Google Chrome prior to 115.0.5790.170 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page

CVE-2023-40694 of 4 sources documented this
30

rank 30 = 6 + 22 + 0 + 2 + 0

rank@v1 · scheduled

Someone is already using it

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

EPSS 0.24918  ·  without this subject the record ranks 24

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 8.8, from NVD  ·  without this subject the record ranks 8

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 30

How much of the world it touches

NVD CPE configurations

1 product in the CPE ranges  ·  without this subject the record ranks 28

Someone else already set the date

CISA KEV remediation due date

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

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$1.24Mover the next 30 days, if this record is yours
Movement+$1.05Mon 2026-06-23, the last material move, 1 month before this reading
Basisassumeda published average, not your estate

$1.24M = $4.99M incident cost x 1 exposure x 0.24918 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.24918EPSSNOT IN KEVas of 2026-09-20
Severity8.8 HIGHreceipt
Harmtotal lossreceipt
Exploitationnone in held sources
Defensefix version namedreceipt
Movementdoubled within 72hreceipt
PLATEAU10Minimal movement since 2026-06-23, 41 days at 0.25, as of 2026-08-03. arc-rules@v1

Foresight · where to check next

This record is one instance of CWE-843, access of resource using incompatible type ('type confusion'). The index holds 924 prior instances of this class, 42 KEV-listed. taxonomy@v1

Full pattern panel

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

Running Google Chrome? 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 · user interaction required · low attack complexityreceipt
ImpactComplete confidentiality, integrity and availability lossreceipt
Scored fromCVSS v3.1 · NVD's vectorreceipt
Weakness classCWE-843 Access of Resource Using Incompatible Type ('Type Confusion')receipt
Published consequencesCWE-843: Availability, Integrity, Confidentiality: Read Memory, Modify Memory, Execute Unauthorized Code or Commands, DoS: Crash, Exit, or Restart[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

Fixed in115.0.5790.170receipt
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, NVD8.8 HIGHreceipt
Exploit probability0.24918 · top 2% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned byChromereceipt
Recorded changes69 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productGoogle Chromereceipt
Published rangesgoogle chrome < 115.0.5790.170receipt
Fixed in115.0.5790.170receipt

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

Type Confusion in V8 in Google Chrome prior to 115.0.5790.170 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High) receipt

NVD's analysis a second authority

severity
8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
weakness
CWE-843
affected versions
google chrome < 115.0.5790.170

check it yourself chromereleases.googleblog.com crbug.com debian.org lists.fedoraproject.org security.gentoo.org security.gentoo.org +1 morereceipt

Dated events

2025-03-17EPSS moved 0.01 to 0.072025-03-19EPSS moved 0.07 to 0.372026-06-23EPSS moved 0.03 to 0.24

Movement the material steps

3 Aug 20230.00047
17 Mar 20250.07366 · scoring model v2025.03.14
19 Mar 20250.37144 · crossed 0.10
20 Mar 20250.07366 · crossed 0.10
27 Mar 20250.37144 · crossed 0.10
28 Mar 20250.07366 · crossed 0.10
29 Mar 20250.37144 · crossed 0.10
30 Mar 20250.07366 · crossed 0.10
15 Jun 20260.0301 · scoring model v2026.06.15
23 Jun 20260.24116 · crossed 0.10
3 Aug 20260.24918

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

Show all 69 observations
3 Aug 20230.00047
5 Aug 20230.00083
12 Aug 20230.00082
26 Nov 20230.00127
23 Dec 20230.00222
8 Feb 20240.00229
3 Jul 20240.00266
9 Aug 20240.00702
4 Sep 20240.00834
7 Nov 20240.00948
17 Dec 20240.00955
13 Jan 20250.01123
23 Feb 20250.01475
17 Mar 20250.07366
19 Mar 20250.37144
20 Mar 20250.07366
23 Mar 20250.03193
24 Mar 20250.07366
27 Mar 20250.37144
28 Mar 20250.07366
29 Mar 20250.37144
30 Mar 20250.07366
1 Apr 20250.03193
2 Apr 20250.07366
11 Apr 20250.03193
12 Apr 20250.07366
15 Apr 20250.02166
1 May 20250.02634
4 May 20250.02166
9 May 20250.02634
12 May 20250.02166
13 May 20250.02634
14 May 20250.02166
1 Jun 20250.02634
5 Jun 20250.02166
1 Jul 20250.02634
4 Jul 20250.02166
1 Aug 20250.02634
5 Aug 20250.02166
16 Aug 20250.0165
20 Aug 20250.01606
21 Aug 20250.025
1 Sep 20250.03038
4 Sep 20250.025
23 Sep 20250.03979
1 Oct 20250.04889
4 Oct 20250.03979
1 Nov 20250.04889
4 Nov 20250.03979
12 Nov 20250.0281
18 Nov 20250.07366
21 Nov 20250.0281
1 Dec 20250.02581
4 Dec 20250.0281
26 Dec 20250.03979
27 Dec 20250.05307
1 Jan 20260.06493
4 Jan 20260.05307
1 Feb 20260.06493
4 Feb 20260.05307
20 Feb 20260.05445
1 Mar 20260.06659
4 Mar 20260.05445
7 Mar 20260.05307
14 Mar 20260.04207
28 Apr 20260.04412
15 Jun 20260.0301
23 Jun 20260.24116
3 Aug 20260.24918

69 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.24918Published2023-08-03Index as of2026-08-03

Exploit probability more than doubled between 2025-03-17 and 2025-03-19 (0.07366 → 0.37144) and the record had been public for 3 years when this index was last written.

Published 2023-08-03 receipt · Index as of 2026-08-03 derived

The pattern, elsewhere

This record is one instance of CWE-843, access of resource using incompatible type ('type confusion'). The index holds 924 prior instances of this class, 42 KEV-listed. [email protected]

CVE-2023-2033 · Google Chromematches 9 of 9KEV listed · 2023receipt
CVE-2023-3079 · Google Chromematches 9 of 9KEV listed · 2023receipt
CVE-2023-4762 · Google Chromematches 9 of 9KEV listed · 2023receipt
CVE-2022-1096 · Google Chromematches 9 of 9KEV listed · 2022receipt
CVE-2022-1364 · Google Chromematches 9 of 9KEV listed · 2022receipt
CVE-2022-3723 · Google Chromematches 9 of 9KEV listed · 2022receipt

924 records in this class held. The six above are ranked by exploit maturity, then recency.

Siblings and hubs

Records related to this one

Browse the index from here

These are index-wide views, not findings about CVE-2023-4069.

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.