EUVD-2026-50835
GHSA-4xr6-2mhc-hp25
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCompromise renderer via separate bug
-
DeliveryServe crafted HTML page
-
ExploitTrigger race in Downloads component
-
ExecutionWin timing window across process boundary
-
PersistEscape sandbox into browser process
-
ImpactExecute with elevated privileges
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V15 - Secure Coding and Architecture Concurrency control, locking
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 | Exploitation requires that the attacker has ALREADY compromised the renderer process (a prior renderer-RCE primitive is a hard prerequisite), the victim runs Chrome on macOS at a version below 151.0.7922.72, and the user loads/interacts with attacker-controlled content (CVSS UI:R). The vulnerable code path is the Downloads component, and success depends on winning a timing race, which adds non-determinism. Limiting factors: it is not a standalone remote exploit (no renderer compromise, no escape), it is platform-specific to Mac, it needs user interaction, and CISA SSVC marks it not automatable - all of which constrain realistic exploitation to skilled, targeted chains rather than widespread automated attacks. |
| Impact | The raw CVSS 3.1 score of 9.6 (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H) reflects a scope change and total impact, but that score is misleading in isolation because it presumes a fresh network attacker, whereas the description explicitly requires the attacker to have ALREADY compromised the renderer process - this is a second-stage sandbox-escape primitive, not a single-shot remote takeover. Corroborating signals point to lower real-world urgency: EPSS is only 0.23% (14th percentile), CISA SSVC lists Exploitation as 'none' and Automatable 'no' (though Technical Impact is 'total', consistent with a full sandbox escape), and there is no KEV listing and no known POC. The one genuine amplifier is that renderer compromises are common in exploit chains, so a reliable sandbox-escape link like this has real value to sophisticated actors even if not mass-exploited. Note a data tension worth flagging: the tags label this 'Information Disclosure', but the description and CVSS (I:H/A:H, scope change) describe a full sandbox escape - treat the tag as imprecise and defer to the sandbox-escape framing. |
| Exploit ScenarioDerived | An attacker first exploits a separate renderer bug (e.g., a V8 or DOM flaw) to gain code execution inside Chrome's sandboxed renderer on a Mac, then serves a crafted HTML page that drives the Downloads code into its race window to escape the sandbox into the higher-privileged browser process. No public POC is identified at time of analysis, and the attack requires user interaction (UI:R) plus a working renderer compromise, so it fits targeted chain-based exploitation rather than opportunistic mass attacks. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 30, 2026
Sandbox escape in Google Chrome on macOS prior to 151.0.7922.72 lets a remote attacker who has already compromised the renderer process break out of the browser sandbox via a crafted HTML page that triggers a race condition in the Downloads component. Chromium rates it High severity and the CVSS is 9.6 (scope-changed). This is no public exploit identified at time of analysis; EPSS is low at 0.23% (14th percentile) and CISA SSVC records exploitation status as none.
RemediationAI
Vendor-released patch: Chrome 151.0.7922.72 - upgrade macOS Chrome to 151.0.7922.72 or later via the Stable Channel update (https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html), then fully relaunch the browser so the new binary is loaded, since Chrome applies updates only on restart. In managed fleets, push the update through your MDM/enterprise update policy and confirm the effective version. Because exploitation requires a compromised renderer first, defense-in-depth against the initial renderer break is the meaningful compensating control if you cannot patch immediately: keep Site Isolation enabled (default), avoid disabling the sandbox, and limit exposure to untrusted web content; these have negligible functional trade-offs. There is no product-specific workaround for the race itself, so patching is the only complete fix.
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 flaw is a race condition (CWE-362, concurrent execution using shared resource with improper synchronization) in Chrome's Downloads subsystem, which coordinates between the sandboxed renderer process and the higher-privileged browser process to write files to disk. On macOS the browser process brokers privileged operations on behalf of the renderer; a timing window in how the Downloads code handles concurrent state allows a compromised renderer to manipulate shared resources and cross the process/sandbox boundary. The affected CPE is cpe:2.3:a:google:chrome (all versions below the fix), and this specific bug is scoped to the Mac platform per the vendor description.
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
Network-delivered via crafted page (AV:N) but requires winning a race plus a pre-existing renderer compromise, so AC:H; sandbox escape crosses a trust boundary (S:C) with total impact.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
Lifecycle Timeline
4DescriptionCVE.org
Race in Downloads in Google Chrome on Mac prior to 151.0.7922.72 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)
Executive ViewAI
Google Chrome for macOS prior to version 151.0.7922.72 contains a critical sandbox-bypass vulnerability (CVE-2026-17709) with no current public exploits, but which could allow attackers to escalate browser compromise into full operating-system access. All macOS users require this patch to eliminate a pathway for sophisticated attacks to move from web exploitation to system compromise.
Apply vendor patch.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
VulDB
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
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Race conditions occur when multiple concurrent requests exploit the brief time gap between checking a condition and acting upon it (TOCTOU - Time of Check, Time of Use).
Related Vulnerabilities in Google Chrome Prior to 151.0.7922.72 Security Flaws
View all 80Same weakness CWE-362 – Race Condition
View allSame technique Information Disclosure
View allVendor StatusVendor
SUSE
Severity: Critical| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| openSUSE Leap 16.0 | Fixed |
| SUSE Package Hub 15 SP7 | Affected |
Exploit-DB