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

CVE-2026-17710 has a CVSS 3.1 base score of 9.6 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H. EPSS exploitation probability: 0.3%.

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

Google Chrome for macOS contains a critical sandbox escape vulnerability (CVE-2026-17710, CVSS 9.6) that allows attackers who have already compromised the renderer process to escalate privileges to…. A patch is available.

How to fix or mitigate CVE-2026-17710?

Within 24 hours, audit Chrome versions across all macOS endpoints using your asset management or MDM system and notify users of the available patch. Within 7 days, deploy Chrome 151.0.7922.72 or later to all macOS systems through your standard patch mechanism, prioritizing high-risk user groups and servers. Within 30 days, confirm 100% patch deployment coverage, verify no systems remain on versions prior to 151.0.7922.72, and document completion in your change management system.

Google Chrome CVE-2026-17710

EUVD-2026-50836 CRITICAL

Protection Mechanism Failure (CWE-693)

2026-07-30 Chrome

GHSA-j6wg-9fv2-p5wc

Information Disclosure Google

9.6

CVSS 3.1 · Vendor: Chrome

Severity by source

Vendor (Chrome) PRIMARY

9.6 CRITICAL

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

vuln.today AI

8.3 HIGH

Raised to AC:H because a successful escape presupposes prior renderer compromise plus a crafted page; scope Changed as the sandbox boundary is crossed, with full C/I/A impact on the browser process.

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

4.0 AV:N/AC:H/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

SUSE

CRITICAL

qualitative

Red Hat

9.0 HIGH

qualitative

Primary rating from Vendor (Chrome).

CVSS VectorVendor: Chrome

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Jul 30, 2026 - 18:33 vuln.today

CVSS changed

Jul 30, 2026 - 16:37 NVD

9.6 (CRITICAL)

Patch available

Jul 30, 2026 - 02:02 EUVD

CVE Published

Jul 30, 2026 - 00:19 cve.org

UNKNOWN (no severity yet)

CVE Published

Jul 30, 2026 - 00:19 cve.org

CRITICAL 9.6

DescriptionCVE.org

Inappropriate implementation in MHTML 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)

AnalysisAI

Sandbox escape in Google Chrome for macOS prior to 151.0.7922.72 lets an attacker who has already compromised the renderer process break out of the sandbox and reach the more-privileged browser process by loading a crafted HTML page that abuses Chrome's MHTML handling. It is rated High by Chromium and carries a CVSS 9.6 (scope-changed) score, but exploitation is a second-stage step that presupposes prior renderer compromise. There is no public exploit identified at time of analysis, and EPSS is low at 0.29% (21st percentile).

Technical ContextAI

The flaw lives in Chrome's MHTML (MIME HTML) subsystem, the single-file web-archive format that bundles an HTML page and its resources into one MIME multipart document. It is classified as CWE-693 (Protection Mechanism Failure), meaning a security control - here the renderer sandbox boundary that isolates untrusted web content from the browser process - is implemented inappropriately rather than a classic memory-corruption bug. The affected component is the Chromium/Blink rendering engine as shipped in Google Chrome on macOS (cpe:2.3:a:google:chrome). Because MHTML parsing crosses the renderer/browser trust boundary, an already-compromised renderer can leverage the inappropriate implementation to influence privileged browser-side behavior, which is why the CVSS scope is marked Changed (S:C).

RemediationAI

Vendor-released patch: upgrade Google Chrome on macOS 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); Chrome normally auto-updates, so ensure the browser is fully closed and relaunched to apply the new build, and confirm the version under chrome://settings/help. There is no vendor-specified standalone workaround, but because exploitation requires a compromised renderer, the practical compensating controls are those that harden against the first-stage renderer compromise: keep the renderer sandbox enabled (do not launch Chrome with --no-sandbox), enforce Site Isolation, and where policy permits enable Enhanced Safe Browsing to reduce exposure to hostile pages - the trade-off is that none of these fully close the specific MHTML issue, so patching remains the only complete fix. Enterprises can also restrict opening untrusted .mht/.mhtml archives, at the cost of breaking legitimate saved-web-archive workflows.