Google Chrome CVE-2026-11660

Exploitation requires three concrete prerequisites: (1) the attacker must have already compromised the Chrome renderer process - typically via a separate renderer-side RCE delivered through a malicious or attacker-controlled web page; (2) the victim must perform an interaction with the New Tab Page surface (CVSS UI:R), so a fully background drive-by is not in scope; and (3) the target Chrome build must be earlier than 149.0.7827.103 on the desktop stable channel. Limiting factors that reduce realistic risk are the High attack complexity (AC:H), the requirement to chain with a separate renderer bug, and the rapid auto-update cadence of Chrome stable which shortens the exposure window. Authentication is not required against the browser (PR:N), but exploitation is not viable against default, fully-patched Chrome installations.

The CVSS 3.1 score of 8.3 (AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H) reflects a network-reachable, scope-changing, high-impact bug but with High attack complexity and required user interaction, signalling that exploitation is not turnkey. The most important real-world constraint is buried in the description: the attacker must have already compromised the renderer process, meaning this vulnerability is only useful as the second link in an exploit chain (typically paired with a separate renderer RCE). There is no KEV listing, no published EPSS score in the provided data, and no public exploit identified at time of analysis, so urgency is driven by the class of bug (sandbox escape in the world's most-deployed browser) rather than observed exploitation - patch on the normal Chrome stable cadence, prioritized for high-value endpoint fleets and journalists/executives who are realistic targets of chained browser exploits.

An attacker lures a target to a malicious or compromised site that first triggers a separate renderer-process RCE (a common precondition for modern Chromium sandbox escapes), then serves crafted HTML that abuses the New Tab Page's improperly validated input handling to cross from the sandboxed renderer into the browser process. Once outside the sandbox, the attacker executes code with the browser's privileges on the host, enabling credential theft, persistence, or lateral movement. No public exploit identified at time of analysis, but the AC:H/UI:R vector and the renderer-compromise precondition mean realistic abuse is by capable actors chaining bugs rather than commodity malware.