Sandbox escape via Skia heap buffer overflow
Published Jul 1, 2026 · Updated Jul 1, 2026
A Skia heap buffer overflow in Google Chrome before 150.0.7871.46 allows attackers with a compromised renderer to escape the sandbox via crafted HTML. Google identifies Skia as the locus, but the restricted issue report leaves the triggering allocation or bounds-checking error undisclosed. Exploitation requires crafted-page processing after renderer compromise and crosses the browser sandbox boundary into a more privileged process.
Summary
What happened
A Skia heap buffer overflow in Google Chrome before 150.0.7871.46 allows attackers with a compromised renderer to escape the sandbox via crafted HTML. Google identifies Skia as the locus, but the restricted issue report leaves the triggering allocation or bounds-checking error undisclosed. Exploitation requires crafted-page processing after renderer compromise and crosses the browser sandbox boundary into a more privileged process.
The record
- CVE
- CVE-2026-14427
- Published
- Jul 1, 2026
- Updated
- Jul 1, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-122, T1068
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 1, 2026CVE publishedPublication date reported by the CVE source.
- Jul 1, 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.46 <150.0.7871.46
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