Memory disclosure via Media out-of-bounds read
Published Feb 23, 2026 · Updated Feb 23, 2026
Out-of-bounds read in Google Chrome before 145.0.7632.116 allows remote attackers to read process memory via crafted HTML. Google identifies the Media component but keeps the issue details restricted, so the exact parsing locus and operation that crosses the buffer boundary are undisclosed. Rendering a crafted page is required; the published record establishes a memory read but does not document code execution.
Summary
What happened
Out-of-bounds read in Google Chrome before 145.0.7632.116 allows remote attackers to read process memory via crafted HTML. Google identifies the Media component but keeps the issue details restricted, so the exact parsing locus and operation that crosses the buffer boundary are undisclosed. Rendering a crafted page is required; the published record establishes a memory read but does not document code execution.
The record
- CVE
- CVE-2026-3061
- Published
- Feb 23, 2026
- Updated
- Feb 23, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-125
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 23, 2026CVE publishedPublication date reported by the CVE source.
- Feb 23, 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.116 <145.0.7632.116
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.
Weakness, pattern, technique
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