Skip to content
Fencer Vulns
high 8.3

CVE-2024-5274 kev in the critical feed json

Type Confusion in V8 in Google Chrome prior to 125.0.6422.112 allowed a remote attacker to execute arbitrary code inside a sandbox via a cr…

published 2024-05-28 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-46510

cvss
8.3
version 3.1, CNA
cisa kev
Exploited
added 2024-05-28
epss
7.7%
EPSS 7.7% chance of exploitation in 30 days, percentile 94%
public exploits
0
none known

Summary

Type Confusion in V8 in Google Chrome prior to 125.0.6422.112 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)

Patch / fix

cisa required action Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

  • Google Chrome 125.0.6422.112
  • chromium Debian 12 125.0.6422.112-1~deb12u1
  • chromium Debian 14, Debian 13 125.0.6422.112-1

debian advisories DEBIAN-CVE-2024-5274

  • chromium openSUSE Tumbleweed 125.0.6422.112-1.1
  • opera openSUSE Leap 15.6 NonFree 110.0.5130.64-lp156.2.6.1
  • opera openSUSE Leap 15.5 NonFree 110.0.5130.39-lp155.3.48.1

opensuse advisories openSUSE-SU-2024:14004-1openSUSE-SU-2024:0156-1openSUSE-SU-2024:0142-1

  • qt6-qtwebengine Alpine 3.24, Alpine 3.23, Alpine 3.22 +2 more 6.6.3-r5

alpine advisories ALPINE-CVE-2024-5274

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2024-5274 updated cvss 8.8

chromium-browser: another type Confusion in V8

  • Red Hat Enterprise Linux 6 chromium-browser
    affected: workaround, no fix planned “Until updated packages are released for Fedora and EPEL, consider temporarily swapping to an alternative web browser such as Firefox or severely restricting activity to sites you known well and trust.”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Timeline

  1. Found exploited as a 0-day (Project Zero)
  2. 0-day patched (Project Zero)
  3. Added to CISA KEV
  4. Published
  5. CISA SSVC: exploitation active
  6. CISA patch deadline

Known exploited

Added
2 y ago
Patch by
2024-06-18 (2 y ago)
Ransomware
Not known
Required action
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Vendor, product
Google, Chromium V8
CISA name
Google Chromium V8 Type Confusion Vulnerability

Zero-day

Detected in real attacks while still unknown to the vendor and the public, per Google Project Zero's 0day In-the-Wild tracker.

Found
2024-05-20
Patched
2024-05-23
Details
project zero tracker

ATT&CK techniques

How it is exploited and what it leads to, in MITRE ATT&CK terms.

  • T1189 Drive-by Compromise exploitation
  • T1203 Exploitation for Client Execution primary impact

kev release 2025-07-28, att&ck v16.1. KEV to ATT&CK mappings by the MITRE Center for Threat-Informed Defense (Mappings Explorer, Apache-2.0). © 2026 The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation. Terms of use

CISA SSVC

Exploitation
Active, exploited in the wild
Automatable
no
Technical impact
total
Assessed
2 y ago

Exploit prediction

7.73% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • issues.chromium.org https://issues.chromium.org/issues/341663589 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CISA ADP 3.1 8.3 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
NVD 3.1 9.6 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
CNA 3.1 8.3 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H

Affected products

  • Google Chrome

Classification

Weakness
  • CWE-843 Access of Resource Using Incompatible Type
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.