Google Chrome CVE-2026-9999

Victim must be running Google Chrome on macOS at a version below 148.0.7778.216, and must be induced to navigate to attacker-controlled HTML (UI:R in the CVSS vector - visiting a page or opening a link suffices, no further clicks required). The exploitable code path lives in ANGLE, so the target must have a functioning graphics pipeline that ANGLE drives (default on macOS); enterprise deployments that have disabled hardware acceleration reduce but do not necessarily eliminate reachability of ANGLE's software paths. No authentication is needed (PR:N). Code execution is bounded to the Chrome sandbox (S:U, and the description explicitly says 'inside a sandbox'), so full host compromise additionally requires a separate sandbox-escape vulnerability that is not part of this CVE.

Signals are mixed and warrant a nuanced read. CVSS 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) reflects a remotely triggerable, low-complexity, unauthenticated bug that requires user interaction (visiting a page) and remains within a single scope - consistent with renderer/GPU-process code execution rather than a host-level compromise. EPSS is very low (0.04%, 12th percentile) and the vulnerability is NOT on the CISA KEV list, indicating no observed mass exploitation. There is no public exploit identified at time of analysis. The description states code runs 'inside a sandbox,' which materially limits real-world impact unless chained with a separate sandbox-escape - defenders should treat this as a high-priority browser patch (Chromium rates it High) but not an active-exploitation emergency. Note the apparent tension: tags include 'Privilege Escalation' and 'RCE,' yet S:U in the CVSS vector indicates no scope change, so the 'privilege escalation' framing likely refers to internal GPU/renderer privilege boundaries rather than OS-level escalation - verify with the upstream Chromium issue tracker entry (issues.chromium.org/issues/513364480) once disclosed.

An attacker hosts a malicious page containing crafted WebGL or canvas content that exercises the vulnerable ANGLE code path and lures a macOS Chrome user to visit it via phishing, malvertising, or a watering-hole compromise. When the page renders, the ANGLE flaw is triggered and the attacker gains arbitrary code execution inside the Chrome GPU/renderer sandbox on the victim's Mac. No public exploit is identified at time of analysis, and meaningful host compromise would require chaining a separate sandbox-escape bug.