Heap corruption via Blink use-after-free
Published Mar 16, 2021 · Updated Oct 21, 2025
Use-after-free in Google Chrome before 89.0.4389.90 allows remote attackers to corrupt heap memory through a crafted HTML page. Google identifies Blink as the affected component but has not disclosed the freed object's type or the lifetime operation that permits its later reuse. Successful exploitation compromises confidentiality, integrity, and availability within Chrome's sandbox; it requires a user to load attacker-controlled HTML.
Summary
What happened
Use-after-free in Google Chrome before 89.0.4389.90 allows remote attackers to corrupt heap memory through a crafted HTML page. Google identifies Blink as the affected component but has not disclosed the freed object's type or the lifetime operation that permits its later reuse. Successful exploitation compromises confidentiality, integrity, and availability within Chrome's sandbox; it requires a user to load attacker-controlled HTML.
The record
- CVE
- CVE-2021-21193
- Published
- Mar 16, 2021
- Updated
- Oct 21, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 12, 2021Exploitation reportedGoogle reports exploitation in the wild
- Mar 16, 2021CVE publishedPublication date reported by the CVE source.
- Nov 3, 2021Exploitation reportedCISA Known Exploited Vulnerabilities Catalog entry
- 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 <89.0.4389.90
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
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 reports exploitation in the wildreported 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