Heap corruption via Media buffer overflow
Published Feb 18, 2026 · Updated Feb 18, 2026
Heap buffer overflow in Google Chrome's Media component before 145.0.7632.109 allows remote attackers to corrupt heap memory via crafted HTML. Google has not disclosed the specific Media code path or the unchecked operation that writes beyond the heap allocation. Exploitation requires a user to open a crafted page; public sources do not establish whether the resulting corruption causes a crash or enables code execution.
Summary
What happened
Heap buffer overflow in Google Chrome's Media component before 145.0.7632.109 allows remote attackers to corrupt heap memory via crafted HTML. Google has not disclosed the specific Media code path or the unchecked operation that writes beyond the heap allocation. Exploitation requires a user to open a crafted page; public sources do not establish whether the resulting corruption causes a crash or enables code execution.
The record
- CVE
- CVE-2026-2650
- Published
- Feb 18, 2026
- Updated
- Feb 18, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-122, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 18, 2026CVE publishedPublication date reported by the CVE source.
- Feb 18, 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.109 <145.0.7632.109
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