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

Use-after-free in Google Chrome GPU on Windows

IdentifiersCVE-2026-9112CWE-416· Use After Free

CVE-2026-9112 is a high-severity use-after-free vulnerability in the GPU component of Google Chrome on Windows prior to 148.0.7778.179. The flaw can be triggered by a remote attacker via a crafted HTML page, causing memory corruption in the GPU-related code path after an object has been freed and then reused. Successful exploitation allows arbitrary code execution within the Chrome sandbox. Chromium classified the issue as High severity.

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 result in arbitrary code execution in the context of the Chrome sandbox on the affected Windows system. The available CVSS v3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) indicates remote exploitation over the network with low attack complexity, no privileges required, user interaction in the form of visiting or rendering a crafted page, and high potential impact to confidentiality, integrity, and availability within the sandboxed browser context.

Mitigation

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

If immediate patching is not possible, reduce exposure by limiting use of untrusted websites and untrusted HTML content on affected Windows Chrome installations, enforcing rapid browser restart after updates, and applying enterprise controls that restrict browsing to trusted destinations where feasible. Standard browser hardening and endpoint exploit mitigations may reduce risk, but no specific workaround short of updating is provided in the available information.

Remediation

Patch, then assume compromise.

Upgrade Google Chrome on Windows to version 148.0.7778.179 or later. Organizations using Chromium-based packages should apply the corresponding vendor updates that incorporate the fix for CVE-2026-9112. Because Google indicated that technical details may remain restricted until broad patch adoption, standard remediation should prioritize rapid browser update deployment and restart of affected browser instances.
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.