Vulnerability record · CVE-2024-5274 · published 28 May 2024
CVE-2024-5274: Google Chrome V8 type confusion allows sandbox code execution
Google · Chrome
Google Chrome before 125.0.6422.112 contains a type confusion flaw in the V8 JavaScript engine. A crafted HTML page can trigger the confusion and lead to arbitrary code execution inside the browser sandbox. The issue is rated critical by CVSS and was added to CISA KEV, so it warrants urgent patching.
Description
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)
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Automated analysis
critical priorityCVSS 9.6, CISA KEV listing with known exploitation, and remote code execution in a widely deployed browser make this an urgent patch-first issue.
What it is
Google Chrome before 125.0.6422.112 contains a type confusion flaw in the V8 JavaScript engine. A crafted HTML page can trigger the confusion and lead to arbitrary code execution inside the browser sandbox. The issue is rated critical by CVSS and was added to CISA KEV, so it warrants urgent patching.
Impact
An attacker who gets a victim to load a malicious page can execute arbitrary code within the Chrome sandbox, potentially leading to data theft or further compromise of the host. The CVSS vector shows high confidentiality, integrity and availability impact with scope change.
Attack surface
Reached over the network via a crafted HTML page rendered in Chrome; no authentication is required, but user interaction (opening the page) is needed per the CVSS vector UI:R.
Exploitation
CISA added this to the Known Exploited Vulnerabilities catalog on 2024-05-28 with a due date of 2024-06-18, and a Chromium issue reference is tagged Exploit, indicating active exploitation. EPSS 30-day probability is 0.07472 (94th percentile), consistent with observed exploitation.
What to do
- Update Google Chrome to 125.0.6422.112 or later immediately.
- Apply the corresponding Fedora package updates for Chromium/Chrome.
- If patching cannot be completed, follow CISA guidance to discontinue use of the affected product or apply vendor mitigations.
- Enforce automatic browser updates and verify version compliance across endpoints.
- Restrict browsing of untrusted sites or isolate browser sessions until patched.
Detection
- Monitor for Chrome processes spawning unexpected child processes or making anomalous network connections.
- Hunt for crashes or exploit indicators in Chrome/V8 logs matching the referenced Chromium issue.
- Check endpoint telemetry for known exploitation patterns against CVE-2024-5274 in browser sandbox escapes.
- Track version inventory to identify unpatched Chrome installations below 125.0.6422.112.
This assessment is produced automatically and is not human-reviewed. Verify against the vendor advisory before acting on it.
Exploitation in the wild
CISA added CVE-2024-5274 to the Known Exploited Vulnerabilities catalog on 28 May 2024 as "Google Chromium V8 Type Confusion Vulnerability". Required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. Federal deadline 18 June 2024.
Affected products
2 vulnerable configurations from NVD's CPE data, grouped by vendor and product.
References
Track CVE-2024-5274 inside VULONE
Watch it alongside the ransomware crews, C2 infrastructure and forum chatter that reference it, query it through the API and pull it into your SIEM over TAXII.
Related vulnerabilities
Same products first, then exploited flaws of the same weakness class.
Source: NIST National Vulnerability Database (record CVE-2024-5274), CISA KEV, FIRST EPSS (scores of 2026-09-26). This page is refreshed as NVD updates the record.