Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
High

Type Confusion in GFX in Google Chrome

IdentifiersCVE-2026-9117CWE-843· Access of Resource Using…

CVE-2026-9117 is a high-severity type confusion vulnerability in the GFX component of Google Chrome affecting Chrome on Linux and ChromeOS prior to version 148.0.7778.179. According to the provided content, a remote attacker who has already compromised the renderer process can potentially leverage the flaw via a crafted video file to achieve a sandbox escape. The issue is described by Chromium as a type confusion bug in graphics-related processing, but no further public detail about the specific vulnerable function or code path is available in the provided material.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can allow an attacker to break out of Chrome's renderer sandbox on affected Linux and ChromeOS systems. In practical terms, this can turn a renderer compromise into execution or influence beyond the intended sandbox boundary, enabling access to broader browser or host resources than would otherwise be permitted. The provided content does not specify the exact post-escape privileges or follow-on actions.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure by limiting use of untrusted or externally supplied video content in Chrome, restricting execution of Chrome on sensitive Linux and ChromeOS systems, and applying defense-in-depth controls that make renderer compromise and post-compromise chaining harder. Because exploitation requires a prior renderer compromise, mitigations that reduce the likelihood of renderer exploitation also reduce risk. However, patching is the primary mitigation.

Remediation

Patch, then assume compromise.

Update Google Chrome/Chromium to a fixed release. The provided content states the issue affects Chrome on Linux and ChromeOS prior to 148.0.7778.179, so affected systems should be upgraded to version 148.0.7778.179 or later. Ensure the browser is fully restarted after updating so the patched binaries are in use.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GoogleChromeapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity3

Community discussion across Reddit, Mastodon, and other social sources.