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

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

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

Google Chrome versions prior to 150.0.7871.47 contain a critical sandbox escape that allows attackers with renderer-process access to escalate privileges and compromise the host system.. A patch is available.

How to fix or mitigate CVE-2026-13782?

Within 24 hours: Inventory all systems running Chrome and deploy Chrome 150.0.7871.47 to staging/testing environment. Within 7 days: Complete rollout of Chrome 150.0.7871.47 to all user endpoints using standard patch management processes. Within 30 days: Audit deployment compliance and confirm retirement of all unsupported versions below 150.0.7871.47.

Google Chrome CVE-2026-13782

EUVD-2026-40468 CRITICAL

Use After Free (CWE-416)

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

GHSA-ggvw-w797-p3rr

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

10.0

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

10.0 CRITICAL

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

vuln.today AI

8.3 HIGH

AC:H and UI:R because a prior renderer compromise plus victim page load are required; S:C for sandbox escape into the higher-privileged Browser process with full C/I/A impact.

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:P/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 NVD.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Jul 01, 2026 - 16:55 vuln.today

CVSS changed

Jul 01, 2026 - 16:52 NVD

10.0 (CRITICAL)

CVE Published

Jun 30, 2026 - 23:16 cve.org

UNKNOWN (no severity yet)

CVE Published

Jun 30, 2026 - 23:16 nvd

CRITICAL 10.0

DescriptionNVD

Use after free in Browser in Google Chrome prior to 150.0.7871.47 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 desktop versions prior to 150.0.7871.47 lets a remote attacker who has already compromised the renderer process break out of the sandbox and gain broader code execution on the host via a crafted HTML page. Chromium rates the underlying use-after-free as Critical, though there is no public exploit identified at time of analysis and EPSS exploitation probability is low (0.21%). A vendor patch is available and the flaw is a classic second-stage chain component rather than a standalone entry point.

Technical ContextAI

The defect is a CWE-416 use-after-free in Chrome's privileged Browser process (not the renderer), the component responsible for coordinating tabs, IPC, and access to OS resources on behalf of sandboxed renderers. Because the Browser process runs outside the renderer sandbox, memory corruption there can be leveraged to escape the sandbox boundary that normally confines untrusted web content. The affected component is Google Chrome (CPE cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*) across desktop channels below 150.0.7871.47; use-after-free arises when a freed object is subsequently referenced, allowing an attacker with a controlled renderer to manipulate object lifetimes and steer freed-memory reuse toward attacker-controlled execution.

RemediationAI

Vendor-released patch: update Google Chrome to 150.0.7871.47 or later on all desktop platforms, as announced in the Chrome Releases advisory (https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html); Chrome auto-update normally delivers this, so verify via chrome://settings/help and relaunch to apply. Enterprises managing Chrome via policy should push the updated version through their management channel and confirm the reported version is at or above 150.0.7871.47. If immediate patching is not possible, reduce exposure to the renderer-compromise prerequisite by enabling stricter site isolation (already default), restricting untrusted browsing, and deploying enhanced safe browsing to lower the odds of the first-stage renderer exploit - with the trade-off that these controls mitigate the delivery chain rather than the underlying use-after-free itself. Users of Chromium-based browsers should apply the equivalent vendor build once it incorporates the fix.