Skip to content
CTI Academy Sponsor CTI Academy
CRITICAL · CVSS 9.6 CISA Known Exploited Vulnerability

CVE-2024-4947

Google Chromium V8 Type Confusion Vulnerability

Google Chromium V8

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

CVSS
9.6
CRITICAL
EPSS
15.2%
30-day exploitation
Ransomware groups
0
recorded exploiting
Published
15 May 2024
CWE-843

Exploitation status

CISA Known Exploited Vulnerabilities

Listed by CISA on 20 May 2024. US federal agencies were required to remediate it by 10 June 2024.

EPSS — exploitation probability

FIRST puts the probability of exploitation activity in the next 30 days at 15.2%, which is higher than 96.8% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Frequently asked questions

Is CVE-2024-4947 being exploited by ransomware groups?

No ransomware group in this database is currently recorded as exploiting CVE-2024-4947.

What does CVE-2024-4947 affect?

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

How severe is CVE-2024-4947?

CVE-2024-4947 is rated CRITICAL with a CVSS base score of 9.6. EPSS puts the probability of exploitation in the next 30 days at 15.2%, higher than 96.8% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 10 June 2024.

How should organisations respond to CVE-2024-4947?

Apply the vendor patch for Google Chromium V8 as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.