Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to crafted page
-
DeliveryDeliver malicious media via HTML
-
ExploitTrigger improper Media implementation
-
ExecutionEscape renderer sandbox
-
ImpactExecute arbitrary code as user
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V2 - Validation and Business Logic Input validation, allowlisting
|
| Exploitation Conditions | Exploitation requires the victim to be running Google Chrome on macOS at a version below 151.0.7922.169 and to open a crafted HTML page - user interaction (UI:R) is mandatory, so the attacker must lure the target to attacker-controlled content rather than exploiting passively. No authentication or prior privileges are needed (PR:N), and the attack works over the network against a default Chrome install; the specific trigger is malformed media content handled by Chrome's Media component. Limiting factors: the flaw is scoped to the macOS platform only, the browser must be unpatched, and the single required click is the main gate on mass exploitation. |
| Impact | This is a genuine high priority, not an inflated score. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H = 9.6) indicates network reachability, low complexity, no privileges, only a single user click, and a scope change with total confidentiality/integrity/availability loss - consistent with a browser sandbox escape. No EPSS score, SSVC decision, or CISA KEV entry was provided, so probabilistic exploitation and automatability cannot be quantified from the input, and there is no public exploit identified at time of analysis. The absence of KEV/POC data means active exploitation is NOT confirmed; however, media-component sandbox escapes in Chrome are historically attractive targets and Google's own security team reported this (chrome-cve-admin@google.com), so defenders should treat patching as urgent despite the missing EPSS/KEV signals. Note the platform scope is explicitly macOS only per the description. |
| Exploit ScenarioDerived | An attacker hosts a malicious web page containing crafted media content and lures a macOS Chrome user to visit it via a phishing link, malvertising, or a compromised site. When Chrome's Media component processes the crafted content, the improper implementation is triggered and the attacker executes arbitrary code outside the renderer sandbox, gaining code execution in the user's context on the Mac. No public exploit code is identified at time of analysis, and success requires the victim to open the page (UI:R). |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 19, 2026
Sandbox-escaping remote code execution in Google Chrome for macOS (versions prior to 151.0.7922.169) stems from an improper implementation in the browser's Media component, letting a remote attacker who lures a victim to a crafted HTML page run arbitrary code outside the renderer sandbox. Rated High by Chromium and carrying a 9.6 CVSS with a scope change, this flaw breaks the browser's primary containment boundary, though there is no public exploit identified at time of analysis. Google has shipped a fix in the Stable channel, and only user interaction (visiting a malicious page) is required to trigger it.
RemediationAI
Vendor-released patch: Google Chrome 151.0.7922.169 for macOS - update Chrome immediately via the built-in updater (Chrome menu → About Google Chrome) and relaunch to complete installation, then confirm the version is at or above 151.0.7922.169. In managed fleets, push the update through your MDM/enterprise policy and force a browser restart, since the fix only takes effect after relaunch. There is no vendor-documented configuration workaround for this specific media flaw; as an interim compensating control before the update lands you can restrict exposure by having users avoid untrusted sites and by deploying enterprise policies that limit navigation to trusted domains - though this only reduces, not eliminates, the click-to-exploit risk. Reference Google's advisory at https://chromereleases.googleblog.com/2026/08/stable-channel-update-for-desktop_0826575033.html for release details.
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
The defect lives in Chrome's Media subsystem - the pipeline that decodes and renders audio/video content delivered through HTML (e.g. <video>/<audio> elements and related media APIs). It is classified as CWE-20 (Improper Input Validation), meaning attacker-controlled media data is not correctly validated before processing, producing an 'inappropriate implementation' that can be steered into memory-unsafe or logic-unsafe behavior. Critically, the impact reaches 'outside the sandbox': Chrome normally isolates untrusted web content in a low-privilege renderer process, so a bug that escapes that boundary implies the media handling occurs in, or can pivot to, a higher-privileged (e.g. GPU/browser) process. The affected CPE is Google Chrome on macOS; per the EUVD entry the vulnerable range is all builds before 151.0.7922.169.
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:C/C:H/I:H/A:H
Remote crafted-page delivery (AV:N, AC:L, PR:N) needs one victim click (UI:R); a sandbox escape crosses a trust boundary (S:C) yielding full code execution (C/I/A:H).
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
3DescriptionCVE.org
Inappropriate implementation in Media in Google Chrome on on Mac prior to 151.0.7922.169 allowed a remote attacker to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)
Executive ViewAI
Google Chrome for macOS versions prior to 151.0.7922.169 contains a critical sandbox-escape vulnerability allowing arbitrary code execution when users visit malicious websites. Every macOS user with unpatched Chrome faces immediate risk of complete system compromise, with attackers gaining full access to applications, files, and network credentials on the device. Organizations must prioritize patching as this vulnerability breaks Chrome's core security containment model.
Apply vendor patch: Chrome 151.0.7922.169 or later for macOS
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
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Same weakness CWE-20 – Improper Input Validation
View allVendor StatusVendor
SUSE
Severity: Critical| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| openSUSE Leap 16.0 | Fixed |
| openSUSE Tumbleweed | Fixed |
| SUSE Package Hub 15 SP7 | Affected |
EUVD-2026-61230
GHSA-fcqj-cvcf-3pmv
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB