Skip to main content
Mallory
CriticalExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2024-4947: Type Confusion in Google Chrome V8 Maglev

Published May 15, 2024 · Updated 13 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.6Critical · v3.1
EPSS15.2%97th percentile
CISA KEVYesAdded May 20, 2024
In the wildActivePer CISA KEV
Vendors
GoogleFedora Project
IdentifiersCVE-2024-4947CWE-843 · Access of Resource Using…

CVE-2024-4947 is a type confusion vulnerability in the Maglev optimizing compiler of Google Chrome's V8 JavaScript engine, affecting Chrome versions before 125.0.6422.60. A missing check when storing to module exports enables memory corruption through specially crafted JavaScript delivered in an HTML page. Successful exploitation permits arbitrary memory reads and writes within the V8 sandbox and arbitrary code execution within Chrome's sandboxed execution environment. Google confirmed exploitation in the wild. Lazarus-associated campaigns used the vulnerability in drive-by attacks targeting cryptocurrency users.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

An attacker can compromise the confidentiality and integrity of memory accessible within the affected sandbox and execute arbitrary code in the sandboxed Chrome process. The vulnerability alone does not establish an escape from Chrome's process sandbox or unrestricted control of the operating system. Observed attacks chained it with a separate Irregexp vulnerability to bypass the V8 sandbox, access broader process memory, and overwrite JIT-compiled code with shellcode. A related campaign resulted in Manuscrypt infections.

Mitigation

If you can’t patch tonight, do this now.

If patching is delayed, restrict access to untrusted web content using URL and DNS filtering, maintain browser isolation and exploit-protection controls, and monitor endpoints for browser exploitation. Enforce least privilege and avoid routine browsing with administrative accounts to limit potential downstream compromise. These measures reduce exposure but do not replace the security update.

Remediation

Patch, then assume compromise.

Upgrade Google Chrome to a current supported release. The initial fixed releases were 125.0.6422.60 or 125.0.6422.61 for Windows and macOS, and 125.0.6422.60 for Linux. Enable automatic updates and verify deployment across affected endpoints.

Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Fedora ProjectFedoraoperating_system
GoogleChromeapplication
FAQ

Frequently asked questions

Is CVE-2024-4947 exploited in the wild?
Yes. As of Nov 4, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on May 20, 2024.
Is there a public exploit for CVE-2024-4947?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2024-4947, the earliest disclosed Jul 21, 2025.
Is there a patch for CVE-2024-4947?
Upgrade Google Chrome to a current supported release. The initial fixed releases were 125.0.6422.60 or 125.0.6422.61 for Windows and macOS, and 125.0.6422.60 for Linux.
What products are affected by CVE-2024-4947?
Google Chrome and Fedora Project Fedora.
How severe is CVE-2024-4947?
CVE-2024-4947 has a CVSS v3.1 score of 9.6 (Critical) and an EPSS score of 15.2% (97th percentile) as of Nov 4, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence5Every report linking this CVE to a named adversary.
Associated malware1Malware families linked to this CVE, with evidence and IOCs.
Detection signatures2YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.