Heap corruption via Ozone use after free
Published Jul 14, 2026 · Updated Jul 14, 2026
Use after free in Ozone in Google Chrome on Linux before 150.0.7871.125 allows remote attackers to corrupt heap memory via crafted HTML. Google identifies the affected locus only as Ozone; the restricted Chromium issue does not disclose which object is freed or later dereferenced. A user must open the crafted page and perform specific UI gestures; published evidence establishes heap corruption but does not identify code execution.
Summary
What happened
Use after free in Ozone in Google Chrome on Linux before 150.0.7871.125 allows remote attackers to corrupt heap memory via crafted HTML. Google identifies the affected locus only as Ozone; the restricted Chromium issue does not disclose which object is freed or later dereferenced. A user must open the crafted page and perform specific UI gestures; published evidence establishes heap corruption but does not identify code execution.
The record
- CVE
- CVE-2026-15764
- Published
- Jul 14, 2026
- Updated
- Jul 14, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 14, 2026CVE publishedPublication date reported by the CVE source.
- Jul 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=150.0.7871.125 <150.0.7871.125
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