Google Chrome CVE-2026-121098

Exploitation requires the attacker to FIRST have compromised Chrome's renderer process - this is a sandbox-escape primitive, not a standalone remote entry point - and additionally requires the victim to load attacker-controlled content (UI:R) that reaches the vulnerable GPU code path. The CVSS AC:H indicates conditions beyond the attacker's direct control must align to trigger the improper state validation; the trigger mechanism beyond 'crafted HTML page' and 'improper state validation in GPU' is not described in the available sources. Limiting factors that reduce realistic risk below the 8.3 score: the mandatory prior renderer compromise, required user interaction, and high attack complexity; affected only on versions prior to 157.0.8103.38.

Signals are mixed but point to a genuine, non-emergency priority. The CVSS 3.1 base score is 8.3 (High) with S:C/C:H/I:H/A:H reflecting a full sandbox escape (SSVC Technical Impact: total), but AC:H and UI:R meaningfully dampen real-world exploitability, and the published vector shows PR:N even though the description explicitly requires an attacker who has ALREADY compromised the renderer process - so this is a second-stage chaining bug, not a standalone remote RCE. That conflict should be noted: CVSS PR:N implies no prior privilege, yet the description implies a prerequisite renderer compromise, so treat PR:N as a Chromium scoring convention rather than evidence of trivial unauthenticated exploitation. SSVC reports Exploitation: none and Automatable: no, and the input provides no KEV listing and no EPSS score, which argues against widespread opportunistic exploitation. The vuln.today Decision label is this_week, consistent with a patch-promptly (not drop-everything) posture. Net: a real, high-impact sandbox-escape primitive valuable inside an exploit chain, but gated behind a prior renderer compromise, user interaction, and high attack complexity - patch within the vendor's normal cycle rather than as an active-exploitation emergency.

An attacker who has already achieved code execution inside Chrome's renderer (via a separate renderer bug) lures a victim into loading a crafted HTML page that triggers improper GPU state validation, allowing code to execute outside the sandbox on the host. No public exploit was identified at time of analysis, and the high attack complexity (AC:H) plus required user interaction (UI:R) constrain reliability and reach.