Sandboxed code execution via codec heap overflow
Published May 14, 2026 · Updated May 14, 2026
Heap buffer overflow in Google Chrome Codecs before 148.0.7778.168 allows remote attackers to execute code inside the sandbox via crafted video. Google identifies the Codecs component and heap overwrite class, but the restricted issue record does not disclose the faulty decoder, function, or bounds operation. A user must process attacker-controlled video; exploitation remains inside the browser sandbox unless chained with a separate escape.
Summary
What happened
Heap buffer overflow in Google Chrome Codecs before 148.0.7778.168 allows remote attackers to execute code inside the sandbox via crafted video. Google identifies the Codecs component and heap overwrite class, but the restricted issue record does not disclose the faulty decoder, function, or bounds operation. A user must process attacker-controlled video; exploitation remains inside the browser sandbox unless chained with a separate escape.
The record
- CVE
- CVE-2026-8529
- Published
- May 14, 2026
- Updated
- May 14, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-122, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 14, 2026CVE publishedPublication date reported by the CVE source.
- May 14, 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=148.0.7778.168 <148.0.7778.168
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