Google Chrome CVE-2026-106425

Exploitation requires a chain of specific prerequisites, not a default-configuration remote hit: (1) the attacker must have already compromised a Chrome renderer process, (2) the victim must interact with an attacker-controlled crafted HTML page (UI:R), and (3) social engineering must be used to abuse the BrowserTag component and bypass site isolation. The vulnerable component is BrowserTag in Chrome versions prior to 155.0.8059.39. Limiting factors: the high attack complexity (AC:H), the mandatory user interaction, and especially the pre-existing renderer compromise sharply narrow realistic exploitation to targeted multi-stage attacks; impact is confined to Low confidentiality and Low integrity with no availability effect, and scope is unchanged (S:U).

This is a low-priority, defense-in-depth issue rather than a front-line threat, and the signals are consistent in pointing that way. The CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N, base 4.2 Medium) encodes high attack complexity and required user interaction, with only Low confidentiality and Low integrity impact and no availability impact. Critically, the description establishes a prerequisite the CVSS vector does not fully convey: the attacker must have ALREADY compromised the renderer process, so this is a site-isolation/sandbox-boundary weakening primitive used as one link in a chain, not a standalone remote-code bug. EPSS reinforces low real-world urgency at 0.19% (8th percentile). There is no CISA KEV listing and no public exploit identified, so there is no evidence of active exploitation or weaponization. No SSVC decision data was provided in the input. The main nuance to flag: the vector shows PR:N (no privileges), but the description's 'compromised the renderer process' precondition is a substantial real-world barrier that PR:N understates - Chromium conventionally scores renderer-compromise chains this way, so defenders should read the practical bar as higher than the 4.2 score alone suggests.

An attacker who has already gained code execution in a Chrome renderer process (e.g., via a separate renderer exploit) lures the user into interacting with a crafted HTML page, using that social engineering plus the BrowserTag missing-authorization flaw to bypass site isolation and read or tamper with data belonging to another site/origin. No public exploit code has been identified at time of analysis, and the high complexity plus the requirement of a pre-compromised renderer make this a chain component rather than an initial-access vector.