Google Chrome CVE-2026-113230

Exploitation requires a victim using Google Chrome prior to 156.0.8078.47 to actively load attacker-controlled crafted HTML (navigate to a malicious or compromised page), per UI:R - there is no server-side or passive trigger. No authentication or special configuration is needed (PR:N, default configuration affected), which broadens exposure. The key LIMITING factor is that resulting code execution is confined to the renderer/browser sandbox per the description, so standalone impact on the host is contained unless combined with an additional sandbox-escape vulnerability; user interaction (visiting the page) is also mandatory.

The supplied CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base 8.8) indicates a network-reachable, low-complexity flaw needing no privileges but requiring user interaction - consistent with the description of exploitation via a crafted HTML page that a victim must visit. However, two signals conflict with the raw score: the description states code execution occurs 'inside the sandbox' (not a sandbox escape), and Google/Chromium rated the security severity only 'Medium'. This strongly suggests real-world impact is constrained by Chrome's sandbox, so a single bug of this class typically must be chained with a sandbox-escape to achieve host compromise - the 8.8 overstates standalone risk. No EPSS score, CISA KEV listing, or POC indicator was provided, so there is no evidence of active exploitation or public exploit code. Net assessment: a legitimately patch-worthy browser RCE primitive, but absent KEV/POC/EPSS signals it is a routine high-priority browser-update item rather than an emergency; the sandbox containment and Medium vendor rating argue against treating it as a weaponized, widely-exploited threat.

An attacker hosts or compromises a web page containing crafted HTML that triggers the improper input validation in Chrome's Browser component, and lures a victim (via link, ad, or malvertising) to visit it. When the page loads in an unpatched Chrome (prior to 156.0.8078.47), the flaw yields arbitrary code execution confined to the renderer sandbox. No public exploit was identified in the provided data; real-world host compromise would require chaining this with a separate sandbox-escape bug.