Sandbox escape via GFX type confusion
Published May 20, 2026 · Updated May 20, 2026
Type confusion in Google Chrome GFX before 148.0.7778.179 on Linux and ChromeOS allows remote attackers to escape the sandbox via crafted video. Google identifies GFX as the affected component but has not disclosed the function or the operation that misinterprets video input. Exploitation requires prior control of a renderer process and a crafted video file; the record does not establish a standalone browser compromise.
Summary
What happened
Type confusion in Google Chrome GFX before 148.0.7778.179 on Linux and ChromeOS allows remote attackers to escape the sandbox via crafted video. Google identifies GFX as the affected component but has not disclosed the function or the operation that misinterprets video input. Exploitation requires prior control of a renderer process and a crafted video file; the record does not establish a standalone browser compromise.
The record
- CVE
- CVE-2026-9117
- Published
- May 20, 2026
- Updated
- May 20, 2026
- Vendor
- The fscrypt Project
- Product
- Chrome
- Classifications
- CWE-843, T1068
- 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 version<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.
Activity data is delayed. The latest report is Sep 28, 2026.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us