Google Chrome EUVD-2026-35212

Exploitation has two explicit hard prerequisites derived directly from the CVE description and CVSS vector. First, the attacker must have already compromised the Chrome renderer process on the victim's macOS system via a separate vulnerability - this is not a standalone exploitable issue and cannot be used as an initial access vector. Second, user interaction is required (UI:R per CVSS), meaning the victim must visit or load a crafted HTML page. The vulnerability is platform-scoped to macOS only; Chrome on Windows and Linux are not affected by this specific issue. Attack complexity is High (AC:H), reflecting the multi-stage chain required. Factors limiting exploitation: the renderer compromise prerequisite alone makes this inaccessible to most threat actors; the attack is not automatable per SSVC assessment; and impact is limited to partial confidentiality loss with no write or denial-of-service capability. The PR:N CVSS component indicates no Chrome-level authentication is required, but this is superseded in practice by the renderer compromise prerequisite.

Multiple converging signals place this vulnerability at the low end of real-world priority. The CVSS score of 3.1 is driven by AC:H (high complexity), UI:R (victim must visit crafted page), and C:L (only partial confidentiality loss with no integrity or availability impact). The SSVC framework independently confirms: exploitation is none, the attack is not automatable, and technical impact is only partial. No EPSS score was supplied in the source data, so exploitation probability cannot be quantified. KEV status is absent, meaning CISA has not observed active exploitation. Most critically, the description explicitly requires a pre-compromised renderer - an attacker must have already exploited a separate, more severe vulnerability to gain renderer-level code execution before this flaw becomes relevant. This is not a standalone exploitable issue; it is a second-stage capability in a chained attack. For most organizations on routine patch cycles, this does not constitute an emergency. The primary value to adversaries is bypassing same-origin protections as part of a broader browser exploitation chain targeting macOS users.

An attacker who has already achieved renderer-level code execution in Chrome on macOS - through a separate, more severe exploit such as a renderer RCE vulnerability - serves a specially crafted HTML page to the victim. The crafted page triggers the Dawn input validation flaw, causing the compromised renderer to leak data from a cross-origin context (such as a banking portal or authenticated session) back to the attacker-controlled renderer. No public exploit code exists for this vulnerability at the time of analysis.