Sandbox escape via V8 out-of-bounds memory access
Published Jul 16, 2024 · Updated Mar 20, 2025
Out-of-bounds memory access in V8 in Google Chrome before 126.0.6478.182 allows remote attackers to escape the sandbox via a crafted HTML page. The public record identifies V8 as the locus but does not disclose whether the engine reads or writes beyond a buffer or name the affected code path. Exploitation requires a user to load the crafted page; successful sandbox escape permits code to operate outside the renderer sandbox.
Summary
What happened
Out-of-bounds memory access in V8 in Google Chrome before 126.0.6478.182 allows remote attackers to escape the sandbox via a crafted HTML page. The public record identifies V8 as the locus but does not disclose whether the engine reads or writes beyond a buffer or name the affected code path. Exploitation requires a user to load the crafted page; successful sandbox escape permits code to operate outside the renderer sandbox.
The record
- CVE
- CVE-2024-6779
- Published
- Jul 16, 2024
- Updated
- Mar 20, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-787, CWE-125, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 16, 2024CVE publishedPublication date reported by the CVE source.
- Mar 20, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <126.0.6478.182
- Affected versionversion=126.0.6478.182 <126.0.6478.182
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo