Skip to main content
Mallory
UnratedVulnerability

CVE-2024-9370: V8 Maglev Escape Analysis Incorrect Optimization

Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Google
IdentifiersCVE-2024-9370CWE-682

CVE-2024-9370 is a high-severity incorrect-optimization vulnerability in the V8 JavaScript engine used by Google Chrome. Maglev escape analysis can incorrectly elide an inlined allocation for a constructor’s receiver object when the constructor returns a primitive and no subsequent use of the receiver is visible to the optimizer. If Error() is invoked in that constructor, stack traversal can encounter the elided receiver and violate a V8 materialization invariant, resulting in a CHECK failure. The invariant violation may be exploitable for memory corruption and arbitrary code execution in the renderer process.

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.

A remote attacker can induce renderer-process memory corruption and potentially execute arbitrary code in the context of the affected browser renderer by convincing a user to load attacker-controlled web content. The stated CVSS v3.1 impact is high for confidentiality, integrity, and availability. Renderer execution is subject to Chrome sandboxing; full operating-system compromise would generally require an additional sandbox-escape vulnerability or another means of privilege expansion.

Mitigation

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

Apply the vendor update promptly. Until updates are deployed, reduce exposure to untrusted web content, enforce least privilege for browser users, restrict untrusted JavaScript and browser extensions where operationally feasible, and use URL/DNS filtering and endpoint exploit-protection controls. These measures reduce exposure but do not correct the vulnerable V8 optimization.

Remediation

Patch, then assume compromise.

Update Google Chrome to 129.0.6668.89 or later on Linux, or 129.0.6668.89/129.0.6668.90 or later on Windows and macOS, as appropriate for the supported release channel. Gentoo users should upgrade affected browser packages to the fixed versions specified by GLSA-202608-29, including Chromium and Google Chrome 131.0.6778.85 or later, Microsoft Edge 131.0.2903.63 or later, and Opera 116.0.5366.21 or later.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
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
GoogleChromeapplication
FAQ

Frequently asked questions

Is CVE-2024-9370 exploited in the wild?
As of Sep 26, 2026, Mallory has no reports of CVE-2024-9370 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2024-9370?
As of Sep 26, 2026, Mallory has found no public exploit for CVE-2024-9370.
Is there a patch for CVE-2024-9370?
Update Google Chrome to 129.0.6668.89 or later on Linux, or 129.0.6668.89/129.0.6668.90 or later on Windows and macOS, as appropriate for the supported release channel. Gentoo users should upgrade affected browser packages to the fixed versions specified by GLSA-202608-29, including Chromium and Google Chrome 131.0.6778.85 or later, Microsoft Edge 131.0.2903.63 or later, and Opera 116.0.5366.21 or later.
What products are affected by CVE-2024-9370?
Google Chrome.
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 evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.