Google Chrome EUVD-2026-34740

Exploitation requires the victim to actively open a crafted HTML page in Chrome prior to 149.0.7827.53 (UI:R confirmed in CVSS vector) and for Chrome DevTools to process the attacker-controlled content - meaning the user typically must have DevTools open or the page must trigger a code path that invokes DevTools functionality. No authentication is required on the attacker side (PR:N), and no special target-side configuration beyond running a vulnerable Chrome build. Limiting factors: code execution is contained to the renderer sandbox (S:U), so achieving privileged code execution on the host requires chaining a second sandbox escape vulnerability; the DevTools requirement narrows the exposed user population primarily to developers and power users.

The CVSS 8.8 score reflects network attack vector, low complexity, no privileges, and a high impact triad - but UI:R (user interaction required) means the victim must visit attacker-controlled content. Critically, CISA SSVC reports Exploitation: none and Automatable: no, and EPSS data was not provided; Chromium itself classified the bug as 'security severity: Low' despite the high CVSS, which signals the practical exploitability is constrained - likely because the code execution is sandboxed (S:U, scope unchanged) and would need to be chained with a sandbox escape to be meaningful. This is a patch-now-on-normal-cadence issue for managed fleets rather than an emergency, given no KEV listing, no public POC, and the sandbox boundary intact. Note the apparent tension between CVSS:H/H/H and Chromium's 'Low' rating - verify with the Chromium issue tracker entry once the bug becomes public.

An attacker hosts a malicious webpage and lures a target (via phishing email, malvertising, or a watering-hole compromise) to open the page in Chrome with DevTools either auto-triggered or already open during debugging. Crafted HTML on the page triggers the out-of-bounds read in the DevTools parser, which the attacker leverages to corrupt memory and execute shellcode inside the renderer sandbox. No public POC is currently available, and the attacker would still need a separate sandbox escape to achieve full host compromise.