What is the CVSS score of CVE-2026-9885?

CVE-2026-9885 has a CVSS 3.1 base score of 8.3 (High). CVSS vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H. EPSS exploitation probability: 0.0%.

Which versions of Google Chrome are affected by CVE-2026-9885?

Google Chrome on macOS prior to version 148.0.7778.216 contains a sandbox escape vulnerability (CVE-2026-9885, CVSS 8.3) that could allow an attacker with browser-level code execution to gain…. A patch is available.

How to fix or mitigate CVE-2026-9885?

Within 24 hours: identify all macOS devices running Chrome versions prior to 148.0.7778.216 and notify users of patch availability. Within 7 days: deploy Chrome version 148.0.7778.216 or later across all macOS endpoints via your managed software deployment process. Within 30 days: verify 100% compliance through endpoint telemetry and implement continuous monitoring for abnormal Chrome child processes or privilege escalation attempts.

Google Chrome CVE-2026-9885

EUVD-2026-33180 HIGH

Improper Input Validation (CWE-20)

2026-05-28 Chrome

GHSA-hpp8-75j8-prpw

Google Information Disclosure Chrome

8.3

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

8.3 HIGH

AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H

SUSE

HIGH

qualitative

Red Hat

9.0 CRITICAL

qualitative

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

Attack Vector

Network

Attack Complexity

High

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

May 29, 2026 - 16:31 vuln.today

CVSS changed

May 29, 2026 - 16:27 NVD

8.3 (HIGH)

CVE Published

May 28, 2026 - 22:25 nvd

UNKNOWN (no severity yet)

CVE Published

May 28, 2026 - 22:25 nvd

HIGH 8.3

DescriptionCVE.org

Insufficient validation of untrusted input in UI in Google Chrome on Mac prior to 148.0.7778.216 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Critical)

AnalysisAI

Sandbox escape in Google Chrome on macOS prior to 148.0.7778.216 allows a remote attacker who has already compromised the renderer process to break out of the browser sandbox via a crafted HTML page that abuses insufficient UI input validation. Chromium rates the underlying issue Critical, though current intelligence shows no public exploit identified at time of analysis and a very low EPSS score (0.05%, 15th percentile), indicating the bug is patched before broad weaponization. Exploitation requires chaining with a separate renderer compromise and user interaction, raising the practical bar despite the high CVSS of 8.3.

Technical ContextAI

The flaw resides in Chrome's UI layer on macOS and is classified as CWE-20 (Improper Input Validation), meaning the browser's UI surface accepts and acts on attacker-controlled data from a renderer without sufficient sanity checks. Chrome's multi-process security model relies on the sandboxed renderer being unable to influence higher-privilege browser/UI processes except through tightly validated IPC; a flaw here breaks that trust boundary and is what makes a sandbox escape possible. The affected CPE is cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:* with the macOS build of Chrome specifically called out by the vendor, suggesting platform-specific UI handling code (likely Cocoa/AppKit integration) is involved.

RemediationAI

Vendor-released patch: Google Chrome 148.0.7778.216 for macOS - upgrade affected endpoints to this version or later via the Stable channel update described at https://chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop_0877304591.html and validate via chrome://settings/help. Enterprises managing Chrome via MDM (Jamf, Intune, Kandji) should push the updated package and force a restart to ensure the new build is loaded. As a compensating control until patching completes, restrict users from visiting untrusted sites via web filtering or enforce Site Isolation and Safe Browsing Enhanced Protection through enterprise policy; these reduce but do not eliminate exposure because the bug only triggers after a renderer compromise, so blocking the initial renderer exploit vector (e.g. ad-blocking, script restrictions on untrusted origins) is the most useful pre-patch mitigation, at the cost of some site breakage.