Skip to main content

Google Chrome EUVDEUVD-2026-35216

| CVE-2026-11690 HIGH
Out-of-bounds Read (CWE-125)
2026-06-09 chrome-cve-admin@google.com GHSA-4m7c-c75j-4g7g
7.5
CVSS 3.1 · Vendor: google
Share

Severity by source

Vendor (google) PRIMARY
7.5 HIGH
AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
SUSE
CRITICAL
qualitative
Red Hat
8.0 HIGH
qualitative

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
Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

4
Analysis Generated
Jun 09, 2026 - 02:38 vuln.today
CVSS changed
Jun 09, 2026 - 01:22 NVD
7.5 (HIGH)
CVE Published
Jun 09, 2026 - 00:16 nvd
UNKNOWN (no severity yet)
CVE Published
Jun 09, 2026 - 00:16 nvd
HIGH 7.5

DescriptionCVE.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.

Vendor StatusVendor

SUSE

Severity: Critical
Product Status
openSUSE Leap 16.0 Fixed
openSUSE Tumbleweed Fixed

Share

EUVD-2026-35216 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy