Google Chrome CVE-2026-18015

Exploitation requires the victim to be running Google Chrome on macOS at a version below 151.0.7922.72 and to visit an attacker-controlled HTML page (UI:R - user interaction is mandatory), which must then exercise the WebGPU/Tint shader-translation path. Limiting factors: the bug is macOS-only (Windows/Linux builds are not implicated by the description), it needs the WebGPU-backed Tint code to be reachable, and as a sandbox escape it realistically depends on being combined with a separate renderer-side compromise - consistent with Google's Low severity rating and the very low EPSS despite the 9.6 CVSS. No authentication is required (PR:N).

The signals here conflict and warrant caution. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H) scores 9.6 Critical - network reach, low complexity, no privileges, scope change from a sandbox escape, and full CIA impact - but Google's own Chromium security team rated this Low severity, and EPSS is only 0.16% (6th percentile), indicating very low predicted exploitation. There is no KEV listing and no public exploit identified at time of analysis, so this is not evidence of active or imminent exploitation. The word 'potentially' in the description plus the Low vendor rating suggest practical exploitability is far lower than the 9.6 implies - typical of sandbox-escape bugs, which usually must be chained with a separate renderer compromise. Net: patch on normal Chrome cadence rather than as an emergency; the high CVSS overstates real-world urgency relative to the vendor rating and EPSS.

An attacker hosts a malicious web page containing crafted WebGPU shader code and entices a macOS Chrome user to visit it via a phishing link or malvertising. When the page's shaders are processed by the vulnerable Tint component, the flawed protection logic is triggered, potentially allowing the attacker to escape the renderer sandbox from an otherwise low-privilege web context. No public proof-of-concept has been identified at time of analysis, and the low attack complexity is offset by the need to chain this with renderer control in practice.