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

CVE-2026-13792 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.2%.

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

Google Chrome for macOS (versions prior to 150.0.7871.47) contains a critical sandbox escape vulnerability that allows remote attackers to execute code with system-level privileges by directing users…. A patch is available.

How to fix or mitigate CVE-2026-13792?

24 hours: Identify all macOS systems running Chrome versions prior to 150.0.7871.47; assess user base and deployment scope. 7 days: Deploy Chrome 150.0.7871.47 or later via managed deployment channels (MDM/endpoint management); prioritize business-critical systems and users in high-risk roles. 30 days: Audit compliance across all macOS devices; enforce auto-update policies to prevent regression.

Google Chrome CVE-2026-13792

EUVD-2026-40478 CRITICAL

Use After Free (CWE-416)

2026-06-30 chrome-cve-admin@google.com

GHSA-cx7m-wf2v-m4f4

Denial Of Service Google Use After Free Memory Corruption Red Hat Suse

9.6

CVSS 3.1 · Vendor: google

Severity by source

Vendor (google) PRIMARY

9.6 CRITICAL

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

vuln.today AI

9.6 CRITICAL

Remote crafted page needs user interaction (UI:R) but no auth (PR:N); sandbox escape crosses the security boundary (S:C) with total impact, matching a High-severity Chrome UAF.

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

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

SUSE

CRITICAL

qualitative

Red Hat

9.6 HIGH

qualitative

Primary rating from Vendor (google).

CVSS VectorVendor: google

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 01, 2026 - 21:31 vuln.today

CVSS changed

Jul 01, 2026 - 19:22 NVD

9.6 (None) 9.6 (CRITICAL)

CVE Published

Jun 30, 2026 - 23:16 cve.org

UNKNOWN (no severity yet)

CVE Published

Jun 30, 2026 - 23:16 cve.org

CRITICAL 9.6

DescriptionCVE.org

Use after free in Touchbar in Google Chrome on Mac prior to 150.0.7871.47 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)

AnalysisAI

Sandbox escape in Google Chrome for macOS versions prior to 150.0.7871.47 stems from a use-after-free in the Touchbar component, letting a remote attacker who lures a victim to a crafted HTML page potentially break out of the renderer sandbox. Reported through Google's internal Chrome security process and rated High by Chromium, it carries a CVSS 9.6 due to scope change and full CIA impact, though there is no public exploit identified at time of analysis and EPSS exploitation probability is low at 0.21%. SSVC assesses current exploitation as none, indicating this is a patch-now-but-not-panic item.

Technical ContextAI

The flaw is a CWE-416 use-after-free in Chrome's Touchbar integration, the macOS-specific UI feature that renders contextual controls on the hardware Touch Bar of MacBook Pro devices. A use-after-free occurs when memory is freed but a dangling pointer continues to reference it, allowing an attacker to reallocate that memory with controlled data and manipulate program flow - a recurring root cause in browser memory-corruption bugs. Because this component bridges renderer-controlled content and privileged native macOS APIs, corrupting it can be leveraged not just for renderer code execution but for a sandbox escape, which is why the scope is marked Changed (S:C) in the CVSS vector. The affected CPE is Google Chrome on the Mac platform only; Windows and Linux builds lack the Touchbar surface.

RemediationAI

Vendor-released patch: update Google Chrome for macOS to 150.0.7871.47 or later via the Stable channel; this is the primary and complete fix, published in Google's Stable Channel Update for Desktop (https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html). Because Chrome auto-updates, ensure the browser is fully closed and relaunched so the update applies, and verify the running version under chrome://settings/help; in managed fleets, push the update through your MDM or enterprise update policy rather than relying on user-initiated restarts. As an interim compensating control on affected Macs, restricting browsing to trusted sites reduces exposure to malicious crafted pages, though it does not eliminate risk; there is no supported feature-level toggle to disable the Touchbar integration within Chrome, so patching is the only reliable remediation and workarounds should be treated as temporary.