Heap corruption via crafted HTML in V8
Published Feb 9, 2021 · Updated Oct 21, 2025
Heap buffer overflow in Google Chrome before 88.0.4324.150 allows remote attackers to corrupt V8 heap memory through a crafted HTML page. Google identifies V8 as the affected component but does not disclose the function, buffer, or bounds-checking operation that fails. A user must load attacker-controlled content, and Google reports that an exploit was used in the wild.
Summary
What happened
Heap buffer overflow in Google Chrome before 88.0.4324.150 allows remote attackers to corrupt V8 heap memory through a crafted HTML page. Google identifies V8 as the affected component but does not disclose the function, buffer, or bounds-checking operation that fails. A user must load attacker-controlled content, and Google reports that an exploit was used in the wild.
The record
- CVE
- CVE-2021-21148
- Published
- Feb 9, 2021
- Updated
- Oct 21, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 9, 2021CVE publishedPublication date reported by the CVE source.
- Oct 21, 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=unspecified <88.0.4324.150
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.
Public exploit references
- Chrome Array Transfer Bypassproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Reported exploitation
- CISA Known Exploited Vulnerabilities Catalog entryknown exploited catalog
- Google reports in-the-wild exploitationreported exploitation
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