Heap corruption via crafted HTML page
Published Mar 20, 2026 · Updated Mar 20, 2026
Heap buffer overflow in Google Chrome CSS before 146.0.7680.153 allows remote attackers to corrupt heap memory via crafted HTML. The public record identifies CSS processing as the locus but does not disclose the malformed construct or bounds operation responsible for the overwrite. A user must open an attacker-controlled page; the disclosed consequence is browser heap corruption, and no more specific end effect is public.
Summary
What happened
Heap buffer overflow in Google Chrome CSS before 146.0.7680.153 allows remote attackers to corrupt heap memory via crafted HTML. The public record identifies CSS processing as the locus but does not disclose the malformed construct or bounds operation responsible for the overwrite. A user must open an attacker-controlled page; the disclosed consequence is browser heap corruption, and no more specific end effect is public.
The record
- CVE
- CVE-2026-4442
- Published
- Mar 20, 2026
- Updated
- Mar 20, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-122, 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?
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