vciy

CVE-2024-7966

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.

Out of bounds memory access in Skia in Google Chrome prior to 128.0.6613.84 allowed a remote attacker who had compromised the renderer process to…

CVE-2024-79664 of 4 sources documented this
39

rank 39 = 15 + 22 + 0 + 2 + 0

rank@v1 · scheduled

Someone is already using it

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

EPSS 0.00669  ·  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 17

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 39

How much of the world it touches

NVD CPE configurations

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

Someone else already set the date

CISA KEV remediation due date

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

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$33,400over the next 30 days, if this record is yours
Movementno material movementthe record holds only daily drift and scoring model releases
Basisassumeda published average, not your estate

$33,400 = $4.99M incident cost x 1 exposure x 0.00669 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.00669EPSSNOT IN KEVas of 2026-09-20
Severity8.8 HIGHreceipt
Harmtotal lossreceipt
Exploitationpublic proof-of-conceptreceipt
Defensefix version namedreceipt
Movementdoubled within 72hreceipt
PLATEAU10Minimal movement since 2024-08-22, 725 days at 0.01, as of 2026-08-17. arc-rules@v1

Foresight · where to check next

Google ChromewebkitgtkApple iOSCVE-2020-29557MicrosoftMicrosoft Office7966

This record is one instance of CWE-119, improper restriction of operations within the bounds of a memory buffer. The index holds 14297 prior instances of this class, 57 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 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-119 Improper Restriction of Operations within the Bounds of a Memory Buffer; CWE-125 Out-of-bounds Readreceipt
Published consequencesCWE-119: Integrity, Confidentiality, Availability: Execute Unauthorized Code or Commands, Modify Memory; Availability, Confidentiality: Read Memory, DoS: Crash, Exit, or Restart, DoS: Resource…[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

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

Fixed in128.0.6613.84receipt
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: Proof-of-concept published · 1 public repository, 2025-07-02.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published · 1 public repository2025-07-02receipt
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, NVD8.8 HIGHreceipt
Exploit probability0.00669 · top 49% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned byChromereceipt
Recorded changes29 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productGoogle Chromereceipt
Published rangesgoogle chrome < 128.0.6613.84receipt
Fixed in128.0.6613.84receipt

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

Out of bounds memory access in Skia in Google Chrome prior to 128.0.6613.84 allowed a remote attacker who had compromised the renderer process to perform out of bounds memory access 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-119; CWE-125
affected versions
google chrome < 128.0.6613.84
also scored by
8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

check it yourself chromereleases.googleblog.com issues.chromium.org receipt

Movement the material steps

22 Aug 20240.00043
17 Mar 20250.00249 · scoring model v2025.03.14
15 Jun 20260.00635 · scoring model v2026.06.15
17 Aug 20260.00669

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

Show all 26 observations
22 Aug 20240.00043
23 Aug 20240.00061
17 Mar 20250.00249
19 Mar 20250.00732
20 Mar 20250.00249
27 Mar 20250.0082
28 Mar 20250.00279
29 Mar 20250.0082
30 Mar 20250.00279
15 Apr 20250.00276
7 May 20250.00289
15 Jun 20250.00229
17 Jun 20250.00242
21 Jun 20250.00223
16 Jul 20250.00255
18 Jul 20250.00349
23 Jul 20250.00277
26 Aug 20250.00349
29 Sep 20250.00926
18 Nov 20250.00406
21 Nov 20250.00926
28 Nov 20250.00853
15 Jun 20260.00635
30 Jul 20260.00673
10 Aug 20260.00664
17 Aug 20260.00669

26 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.00669Published2024-08-21Public PoC2025-07-02Index as of2026-08-17

Exploit probability more than doubled between 2025-03-17 and 2025-03-19 (0.00249 → 0.00732) and the record had been public for 1 year, 11 months when this index was last written.

Published 2024-08-21 receipt · Public PoC 2025-07-02 receipt · Index as of 2026-08-17 derived

The pattern, elsewhere

This record is one instance of CWE-119, improper restriction of operations within the bounds of a memory buffer. The index holds 14297 prior instances of this class, 57 KEV-listed. The nearest of its KEV-listed records are drawn beside this. [email protected]

CVE-2026-3910 · Google Chromematches 9 of 10KEV listed · 2026receipt
CVE-2019-8720 · webkitgtkmatches 8 of 10KEV listed · 2023receipt
CVE-2021-30666 · Apple iOSmatches 8 of 10KEV listed · 2021receipt
CVE-2020-29557matches 7 of 9KEV listed · 2021receipt
CVE-2017-0101 · Microsoft Corporation Windowsmatches 7 of 10KEV listed · 2017receipt
CVE-2017-11882 · Microsoft Officematches 7 of 10KEV listed · 2017receipt

"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

14297 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

google chrome

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-2024-7966.

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.