Severity by source
AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
Primary rating from Vendor (google).
CVSS VectorVendor: google
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
Lifecycle Timeline
4DescriptionCVE.org
Out of bounds read and write in Media in Google Chrome on Mac prior to 149.0.7827.103 allowed a remote attacker who had compromised the renderer process to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)
AnalysisAI
Sandbox-confined arbitrary code execution in Google Chrome on macOS versions prior to 149.0.7827.103 stems from an out-of-bounds read and write in the Media component, exploitable by a remote attacker who has already compromised the renderer process and lures a user to a crafted HTML page. Google rates the Chromium severity as High and has released a patched stable channel update; no public exploit identified at time of analysis, and SSVC reports no observed exploitation.
Technical ContextAI
The flaw resides in Chrome's Media subsystem, which handles audio/video decoding, MediaStream, and related rendering pipelines inside the renderer process on macOS. CWE-125 (Out-of-bounds Read), combined with the description's mention of out-of-bounds write, indicates a memory boundary checking failure in media buffer handling - likely in parsing or processing crafted media content embedded in HTML. Because the bug lives in the renderer sandbox, exploitation yields code execution constrained by Chrome's macOS sandbox, but combined with a prior renderer compromise it forms a link in a multi-stage exploit chain (typically paired with a sandbox escape to reach full system compromise).
RemediationAI
Vendor-released patch: Google Chrome 149.0.7827.103 for macOS - update via the stable channel as documented at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0153744567.html, then restart the browser to activate the new build. For managed fleets, push the update via MDM or Chrome Browser Cloud Management and verify the version via chrome://version. As an interim compensating control prior to patching, restrict browsing to trusted sites and consider enabling Site Isolation strict mode (already default) and disabling unnecessary media features - though disabling media would break legitimate video/audio playback and is rarely tolerable. Administrators should also patch any downstream Chromium-based browsers once their vendors ship the corresponding fix.
Same weakness CWE-125 – Out-of-bounds Read
View allSame technique Information Disclosure
View allVendor StatusVendor
SUSE
Severity: Critical| Product | Status |
|---|---|
| openSUSE Leap 16.0 | Fixed |
| openSUSE Tumbleweed | Fixed |
Share
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-35216
GHSA-4m7c-c75j-4g7g