Heap corruption via TextEncoding use-after-free
Published Mar 11, 2026 · Updated Mar 11, 2026
Use-after-free in TextEncoding in Google Chrome before 146.0.7680.71 allows remote attackers to corrupt heap memory via crafted HTML. TextEncoding reuses or dereferences memory after its lifetime has ended, although the public record does not identify the affected function or object-lifetime error. A user must load attacker-controlled HTML, and the documented consequence is heap corruption rather than a confirmed sandbox escape.
Summary
What happened
Use-after-free in TextEncoding in Google Chrome before 146.0.7680.71 allows remote attackers to corrupt heap memory via crafted HTML. TextEncoding reuses or dereferences memory after its lifetime has ended, although the public record does not identify the affected function or object-lifetime error. A user must load attacker-controlled HTML, and the documented consequence is heap corruption rather than a confirmed sandbox escape.
The record
- CVE
- CVE-2026-3921
- Published
- Mar 11, 2026
- Updated
- Mar 11, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 11, 2026CVE publishedPublication date reported by the CVE source.
- Mar 11, 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.71 <146.0.7680.71
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.
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