Heap corruption via undisclosed V8 implementation flaw
Published Mar 20, 2026 · Updated Mar 20, 2026
Memory corruption in V8 in Google Chrome before 146.0.7680.153 allows remote attackers to trigger heap corruption via crafted HTML. Google identifies the affected locus only as V8 and has not disclosed the incorrect operation because the Chromium issue remains access-restricted. Exploitation requires a user to open attacker-controlled HTML, and the published record establishes heap corruption but not code execution or sandbox escape.
Summary
What happened
Memory corruption in V8 in Google Chrome before 146.0.7680.153 allows remote attackers to trigger heap corruption via crafted HTML. Google identifies the affected locus only as V8 and has not disclosed the incorrect operation because the Chromium issue remains access-restricted. Exploitation requires a user to open attacker-controlled HTML, and the published record establishes heap corruption but not code execution or sandbox escape.
The record
- CVE
- CVE-2026-4461
- Published
- Mar 20, 2026
- Updated
- Mar 20, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 20, 2026CVE publishedPublication date reported by the CVE source.
- Mar 20, 2026Record 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=146.0.7680.153 <146.0.7680.153
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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