Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAttacker hosts crafted HTML page
-
DeliveryLure macOS Chrome user via phishing or malvertising
-
ExploitVictim visits page in vulnerable Chrome
-
ExecutionMalicious WebGL/canvas reaches ANGLE code path
-
PersistTrigger inappropriate-implementation flaw
-
ImpactAchieve arbitrary code execution in GPU/renderer sandbox
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V8 - Authorization Least privilege enforcement
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | 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. |
| Impact | 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. |
| Exploit ScenarioDerived | 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. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – May 29, 2026
Remote code execution in Google Chrome on macOS prior to version 148.0.7778.216 allows a remote attacker to execute arbitrary code within the renderer sandbox by enticing a victim to visit a crafted HTML page that triggers an inappropriate implementation flaw in the ANGLE graphics layer. The issue is rated High by Chromium and carries a CVSS 3.1 score of 8.8 with user interaction required; no public exploit identified at time of analysis and EPSS is low at 0.04%.
RemediationAI
Vendor-released patch: Google Chrome 148.0.7778.216 for macOS - upgrade immediately via the Chrome Stable channel update referenced at https://chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop_0877304591.html. In managed environments, push the update via MDM (Jamf, Intune, Kandji) and force-restart Chrome to apply, since Chrome only completes the update after a relaunch. If patching must be deferred, compensating controls include disabling hardware acceleration in chrome://settings (which reduces ANGLE attack surface at the cost of degraded rendering performance and broken WebGL content), enforcing the SitePerProcess policy and Strict Site Isolation (already default but worth verifying via chrome://policy), and using Chrome Enterprise policies to block untrusted sites or restrict WebGL on high-risk user populations. Track the upstream issue at https://issues.chromium.org/issues/513364480 for further detail once Google removes the view restriction.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
ANGLE (Almost Native Graphics Layer Engine) is the translation layer Chromium uses to convert OpenGL ES API calls into the platform's native graphics API - on macOS this maps to Metal (and historically OpenGL). Because ANGLE handles WebGL and accelerated canvas content from untrusted web pages, flaws in its implementation are directly reachable from JavaScript and have historically been a rich source of GPU-process compromises. The CWE-269 (Improper Privilege Management) classification combined with the description's note that code executes 'inside a sandbox' suggests the bug yields execution in the GPU/renderer process context rather than a full sandbox escape, though privilege handling within the GPU process is implicated. The CPE narrows the affected product to Google Chrome desktop on macOS.
Know when the next one hits your stack
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
Lifecycle Timeline
3DescriptionCVE.org
Inappropriate implementation in ANGLE in Google Chrome on Mac prior to 148.0.7778.216 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)
Executive ViewAI
Google Chrome on macOS contains a high-severity remote code execution vulnerability (CVE-2026-9999, CVSS 8.8) in the ANGLE graphics layer that allows attackers to execute arbitrary code within the browser renderer by tricking users into visiting malicious websites. No public exploit identified at time of analysis, but the vulnerability poses material risk to any macOS Chrome user. Organizations should prioritize patching all macOS Chrome installations to address potential data exfiltration, credential theft, or device compromise.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Same weakness CWE-269 – Improper Privilege Management
View allSame technique Privilege Escalation
View allVendor StatusVendor
SUSE
Severity: High| Product | Status |
|---|---|
| openSUSE Leap 16.0 | Fixed |
| openSUSE Tumbleweed | Fixed |
EUVD-2026-33141
GHSA-qg99-3fxw-j5pv
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB