Heap corruption via CSS use-after-free
Published Feb 11, 2026 · Updated Feb 11, 2026
Use-after-free in Google Chrome's CSS component before 145.0.7632.45 allows remote attackers to corrupt heap memory via crafted HTML. Google identifies the CSS component but has not disclosed the freed object's lifetime error or responsible function because the Chromium issue remains restricted. A user must load attacker-controlled HTML; the published record confirms heap corruption but does not disclose the final exploit primitive.
Summary
What happened
Use-after-free in Google Chrome's CSS component before 145.0.7632.45 allows remote attackers to corrupt heap memory via crafted HTML. Google identifies the CSS component but has not disclosed the freed object's lifetime error or responsible function because the Chromium issue remains restricted. A user must load attacker-controlled HTML; the published record confirms heap corruption but does not disclose the final exploit primitive.
The record
- CVE
- CVE-2026-2313
- Published
- Feb 11, 2026
- Updated
- Feb 11, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 11, 2026CVE publishedPublication date reported by the CVE source.
- Feb 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=145.0.7632.45 <145.0.7632.45
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