Skip to content
CTI Academy Sponsor CTI Academy
HIGH · CVSS 8.8 CISA Known Exploited Vulnerability

CVE-2024-4761

Google Chromium V8 Out-of-Bounds Memory Write Vulnerability

Google Chromium V8

Out of bounds write in V8 in Google Chrome prior to 124.0.6367.207 allowed a remote attacker to perform an out of bounds memory write via a crafted HTML page. (Chromium security severity: High)

CVSS
8.8
HIGH
EPSS
11%
30-day exploitation
Ransomware groups
0
recorded exploiting
Published
14 May 2024
CWE-787

Exploitation status

CISA Known Exploited Vulnerabilities

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

EPSS — exploitation probability

FIRST puts the probability of exploitation activity in the next 30 days at 11%, which is higher than 95.9% 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:U/C:H/I:H/A:H

Frequently asked questions

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

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

What does CVE-2024-4761 affect?

CVE-2024-4761 affects Google Chromium V8. Out of bounds write in V8 in Google Chrome prior to 124.0.6367.207 allowed a remote attacker to perform an out of bounds memory write via a crafted HTML page. (Chromium security severity: High)

How severe is CVE-2024-4761?

CVE-2024-4761 is rated HIGH with a CVSS base score of 8.8. EPSS puts the probability of exploitation in the next 30 days at 11%, higher than 95.9% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 6 June 2024.

How should organisations respond to CVE-2024-4761?

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.