EUVD-2026-35255
GHSA-74g6-5mjw-f8x6
Severity by source
AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Primary rating from NVD.
CVSS VectorNVD
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Lifecycle Timeline
4DescriptionCVE.org
Integer overflow in Media in Google Chrome on Mac prior to 149.0.7827.103 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)
AnalysisAI
Sandbox escape in Google Chrome on macOS prior to version 149.0.7827.103 enables a remote attacker who has already compromised the renderer process to break out of the browser sandbox via a crafted HTML page that triggers an integer overflow in the Media component. Google rates the Chromium severity as High, and no public exploit has been identified at time of analysis. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Attacker must already have code execution inside the Chrome renderer process on macOS (this bug alone is not an initial-access primitive - it is a sandbox-escape link in a chain), the target must be running Chrome on macOS at a version below 149.0.7827.103, and the user must interact by loading a crafted HTML page that exercises the vulnerable Media code path (UI:R in the CVSS vector). … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | Real-world risk is moderate rather than urgent. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker first lands a separate renderer-process RCE (for example via a V8 type-confusion bug delivered through a malvertising network) on a macOS user running pre-149.0.7827.103 Chrome, then loads a second crafted HTML/media payload that triggers the integer overflow in the Media component to escape the renderer sandbox and execute code in a more privileged Chrome process. No public exploit identified at time of analysis, but Chrome sandbox-escape primitives are routinely chained by commercial spyware vendors, so a weaponized chain against high-value macOS targets is plausible. |
| Remediation | Vendor-released patch: Google Chrome 149.0.7827.103 for macOS - upgrade Chrome Stable on all Mac endpoints to 149.0.7827.103 or later via the Chrome Releases stable-channel update (https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0153744567.html), and force-restart the browser so the new binary is actually loaded (a common gap, since Chrome auto-downloads but does not auto-relaunch). … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: Inventory all macOS devices with Google Chrome installed and identify those below version 149.0.7827.103. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Vendor StatusVendor
SUSE
Severity: Critical| Product | Status |
|---|---|
| openSUSE Leap 16.0 | Fixed |
| openSUSE Tumbleweed | Fixed |
Share
External POC / Exploit Code
Leaving vuln.today