Renderer sandbox escape via GFX type confusion
Published May 20, 2026 · Updated May 20, 2026
Type confusion in Google Chrome GFX on Linux and ChromeOS before 148.0.7778.179 allows remote attackers to escape the renderer sandbox. Google has not published the affected GFX code path or the incompatible object types accessed while processing a crafted video file. Exploitation requires a compromised renderer process and user interaction with the crafted file; a successful chain breaks the renderer's isolation.
Summary
What happened
Type confusion in Google Chrome GFX on Linux and ChromeOS before 148.0.7778.179 allows remote attackers to escape the renderer sandbox. Google has not published the affected GFX code path or the incompatible object types accessed while processing a crafted video file. Exploitation requires a compromised renderer process and user interaction with the crafted file; a successful chain breaks the renderer's isolation.
The record
- CVE
- CVE-2026-9117
- Published
- May 20, 2026
- Updated
- May 20, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-843, T1211
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 20, 2026CVE publishedPublication date reported by the CVE source.
- May 20, 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.179 <148.0.7778.179
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