CVE-2024-4947 — Chrome
CRITICALCVE-2024-4947 is a critical-severity (CVSS 9.6) CWE-843 vulnerability. It is in CISA's Known Exploited Vulnerabilities catalog (added 2024-05-20) — treat it as actively exploited and patch now. No vendor fix is recorded yet; mitigation options are listed below.
Exploitation Status
Actively exploited in the wild
- Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2024-05-20. Federal agencies were required to remediate by 2024-06-10.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2024-4947.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2024-4947 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 395,249 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Counts from FIRST.org, log-scaled.
Description
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)
Affected Products
fedorafedoraprojectchromegoogleResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Type Confusion in V8 in Google Chrome prior to 125.0.6422.60 allowed a r…
Type Confusion in V8 in Google Chrome prior to 125.0.6422.60 allowed a r…
Type Confusion in V8 in Google Chrome prior to 125.0.6422.60 allowed a r…
Type Confusion in V8 in Google Chrome prior to 125.0.6422.60 allowed a r…
Type Confusion in V8 in Google Chrome prior to 125.0.6422.60 allowed a r…
Detection & mitigation playbook
VulnerabilityDetect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2024-4947 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Chromium is not shipped in any Red Hat offerings.
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 know well and trust.Source: Red Hat security advisory for CVE-2024-4947 (CC BY 4.0)
Frequently Asked Questions
Is CVE-2024-4947 in your dependencies?
Find it across , including transitive dependencies.