Google Chrome CVE-2026-102321

Exploitation requires the victim to load attacker-controlled HTML/JavaScript in a vulnerable Google Chrome desktop build prior to 154.0.8037.92 - the type-confusion bug is in the V8 JavaScript engine, so any page executing crafted JS in the renderer can trigger it. The key limiting factor is required user interaction (UI:R): the victim must navigate to or render the malicious page (e.g., via a link, ad, or compromised site). No authentication or special privileges are needed (PR:N), and it works against default configurations, but resulting code execution is confined to the renderer sandbox (S:U) - full host compromise would require chaining a separate sandbox-escape vulnerability. Automatic Chrome auto-update to a patched build fully mitigates.

This is a genuine high-priority vulnerability despite mixed exploitation signals. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base 8.8) describes a network-reachable, low-complexity, unauthenticated flaw requiring only that a victim visit a crafted page - the classic drive-by RCE profile for a browser engine. The CWE-843 type confusion in V8 combined with the Chromium 'High' severity rating and 'Technical Impact: total' in SSVC confirms full code execution capability, albeit constrained to inside the renderer sandbox per the description. Counterbalancing this: SSVC reports Exploitation:none and Automatable:no, there is no CISA KEV listing, no EPSS score provided, and no public POC identified - so there is no evidence of active exploitation at time of analysis. The 'inside the sandbox' qualifier is important: this alone yields renderer compromise, not a full host takeover, and would typically need to be chained with a sandbox-escape bug for complete system control (the CVSS S:U/scope-unchanged is consistent with this). Net: treat as a standard-urgency browser patch - high impact and trivially triggerable, but no exploitation-in-the-wild signal, so patch on normal Chrome auto-update cadence rather than emergency response.

An attacker hosts or injects a malicious HTML page containing JavaScript that triggers the V8 type-confusion condition; a victim running a vulnerable Chrome build (<154.0.8037.92) visits the page and the engine misinterprets an object's type, giving the attacker a memory-corruption primitive that executes arbitrary code within the renderer sandbox. No authentication is needed and complexity is low, but the victim must be lured to the page (UI:R). No public exploit code has been identified at time of analysis, and SSVC rates exploitation as none.