Heap corruption via crafted video file
Published Jul 8, 2026 · Updated Jul 8, 2026
Out-of-bounds read and write in Google Chrome Codecs before 150.0.7871.115 allows remote attackers to corrupt heap memory via a crafted video file. The public record names only the Codecs component and does not disclose the affected parser or the bounds-checking error that permits the read and write. Exploitation requires the browser to process a crafted video file; the grounded consequence is heap corruption, with no reported sandbox escape or exploitation in the wild.
Summary
What happened
Out-of-bounds read and write in Google Chrome Codecs before 150.0.7871.115 allows remote attackers to corrupt heap memory via a crafted video file. The public record names only the Codecs component and does not disclose the affected parser or the bounds-checking error that permits the read and write. Exploitation requires the browser to process a crafted video file; the grounded consequence is heap corruption, with no reported sandbox escape or exploitation in the wild.
The record
- CVE
- CVE-2026-15114
- Published
- Jul 8, 2026
- Updated
- Jul 8, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-787, CWE-125, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 8, 2026CVE publishedPublication date reported by the CVE source.
- Jul 8, 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=150.0.7871.115 <150.0.7871.115
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.
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