Code execution via V8 out-of-bounds write
Published May 14, 2024 · Updated Dec 20, 2025
Out-of-bounds write in V8 in Google Chrome before 124.0.6367.207 allows remote attackers to corrupt memory via crafted HTML. Google identifies the locus as the V8 JavaScript and WebAssembly engine but keeps the underlying bug report restricted, so the invalid bounds operation is undisclosed. A victim must load attacker-controlled HTML; successful exploitation executes code in the logged-on user's context, and exploitation has occurred in the wild.
Summary
What happened
Out-of-bounds write in V8 in Google Chrome before 124.0.6367.207 allows remote attackers to corrupt memory via crafted HTML. Google identifies the locus as the V8 JavaScript and WebAssembly engine but keeps the underlying bug report restricted, so the invalid bounds operation is undisclosed. A victim must load attacker-controlled HTML; successful exploitation executes code in the logged-on user's context, and exploitation has occurred in the wild.
The record
- CVE
- CVE-2024-4761
- Published
- May 14, 2024
- Updated
- Dec 20, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-787, T1189, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 14, 2024CVE publishedPublication date reported by the CVE source.
- May 16, 2024Exploitation reportedCISA Known Exploited Vulnerabilities Catalog entry
- Dec 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=124.0.6367.207 <124.0.6367.207
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.
Reported exploitation
- Google report of in-the-wild exploitationreported exploitation
- CISA Known Exploited Vulnerabilities Catalog entryknown exploited catalog
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