# CVE-2026-9117: Google Chrome type confusion in GFX

Source: https://junglewise.ai/threats/cve-2026-9117-google-chrome-type-confusion-in-gfx  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-05-20. Updated: 2026-05-20  
License: CC BY 4.0 with a link back

CVE-2026-9117 · Severity: high · CVSS 7.5 · Published 2026-05-20

Google Chrome and ChromeOS are affected by a security vulnerability in the graphics component. An attacker who has already partially compromised the browser's internal processes could use a specially crafted video file to break out of the security sandbox. This could allow the attacker to gain broader access to the underlying operating system and user data.

Technologies: [Google Chrome](https://junglewise.ai/threats/technologies/chrome), [Google ChromeOS](https://junglewise.ai/threats/technologies/chromeos). Vendors: [Google](https://junglewise.ai/threats/vendors/google).

## Quick answers

**Is CVE-2026-9117 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-9117 being exploited in the wild.

**How severe is CVE-2026-9117?** High severity, with a CVSS score of 7.5, published 20 May 2026.

**Which products and versions are affected?** Google Chrome Prior to 148.0.7778.179; Google ChromeOS Prior to 148.0.7778.179.

**Is there a fix for CVE-2026-9117?** A patch was published on 2026-05-19: Stable channel update released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-9117 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-9117?** Check whether you run Google Chrome or Google ChromeOS at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

A type confusion vulnerability exists in the GFX component of Google Chrome on Linux and ChromeOS. The flaw is triggered when processing a specially crafted video file. An attacker who has already achieved code execution within a compromised renderer process can exploit this vulnerability to perform a sandbox escape. This allows the attacker to execute code with the privileges of the browser process rather than the restricted renderer. The issue is addressed in version 148.0.7778.179 and later.

## Affected products

- Google Chrome Prior to 148.0.7778.179
- Google ChromeOS Prior to 148.0.7778.179

## Timeline

- 2026-04-01: other: Reported by Google internal researchers
- 2026-05-19: patched: Stable channel update released
- 2026-05-20: advisory: NVD publication date

## References

- [https://chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop_0841193308.html](https://chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop_0841193308.html)
- [https://issues.chromium.org/issues/497542537](https://issues.chromium.org/issues/497542537)

## Related threats

- [Google Chrome out of bounds read in Skia](https://junglewise.ai/threats/cve-2026-126922-out-of-bounds-read-in-skia-in-google-chrome-prior-to-157-0-8103)
- [Google Chrome use after free in Accessibility](https://junglewise.ai/threats/cve-2026-126921-use-after-free-in-accessibility-in-google-chrome-prior-to-157-0)
- [Google Chrome information leak in Skia](https://junglewise.ai/threats/cve-2026-126920-information-leak-in-skia-in-google-chrome-prior-to-157-0-8103-78)
- [Google Chrome use-after-free in BrowserTag](https://junglewise.ai/threats/cve-2026-126919-use-after-free-in-browsertag-in-google-chrome-prior-to-157-0)
- [Google Chrome use-after-free in Layout](https://junglewise.ai/threats/cve-2026-126918-use-after-free-in-layout-in-google-chrome-prior-to-157-0-8103-78)