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

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

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

Google Chrome on Windows versions before 150.0.7871.47 contains a privilege-escalation vulnerability (CVSS 8.3) that allows attackers to escape the browser sandbox and gain access to the browser…. A patch is available.

How to fix or mitigate CVE-2026-13829?

Within 24 hours, identify all Windows systems running Google Chrome and their current versions. Within 7 days, deploy Chrome version 150.0.7871.47 or later to all Windows machines; prioritize systems handling sensitive information or frequently visiting untrusted websites. Within 30 days, verify deployment completion through automated inventory tools and enable Chrome's auto-update feature to maintain patch currency.

Google Chrome CVE-2026-13829

EUVD-2026-40515 HIGH

Improper Input Validation (CWE-20)

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

GHSA-wv8r-qr8m-692h

Information Disclosure Google Microsoft Red Hat

8.3

CVSS 3.1 · Vendor: google

Severity by source

Vendor (google) PRIMARY

8.3 HIGH

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

vuln.today AI

8.3 HIGH

AC:H and UI:R reflect the required pre-existing renderer compromise and victim interaction; S:C and high C/I/A capture the sandbox escape into the browser process; PR:N retained as no in-page authentication is needed.

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

HIGH

qualitative

Red Hat

9.0 HIGH

qualitative

Primary rating from Vendor (google).

CVSS VectorVendor: google

Attack Vector

Network

Attack Complexity

High

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Jul 22, 2026 - 19:59 vuln.today

CVE Published

Jun 30, 2026 - 23:16 cve.org

HIGH 8.3

CVE Published

Jun 30, 2026 - 23:16 cve.org

UNKNOWN (no severity yet)

DescriptionCVE.org

Insufficient validation of untrusted input in Settings in Google Chrome on Windows 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: High)

AnalysisAI

Sandbox escape in Google Chrome on Windows before 150.0.7871.47 lets an attacker who has already compromised the renderer process break out of the browser sandbox via a crafted HTML page, escalating from renderer code execution to the more privileged browser process. Rated High severity by Chromium with a CVSS of 8.3 (scope-changing), it stems from insufficient validation of untrusted input in the Settings component. There is no public exploit identified at time of analysis, EPSS is low (0.21%, 11th percentile), and CISA SSVC lists exploitation as none, indicating no observed in-the-wild use despite the total technical impact.

Technical ContextAI

Chrome uses a multi-process architecture where untrusted web content is confined to a low-privilege, sandboxed renderer process, isolated from the higher-privilege browser (broker) process that mediates OS access. This flaw resides in the Settings functionality and is classified as CWE-20 (Improper Input Validation): the browser-side handling accepts untrusted input from the renderer without sufficient validation, allowing a malicious renderer to influence privileged operations and cross the sandbox boundary. The affected component is cpe:2.3:a:google:chrome (all versions prior to the fixed build) on the Windows platform specifically; the CVSS scope change (S:C) reflects that the impact crosses from the renderer sandbox into the browser process trust domain.

RemediationAI

Vendor-released patch: update Google Chrome to 150.0.7871.47 or later on Windows via the Chrome Releases stable channel update (https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html); confirm the browser has restarted so the new build is active, since Chrome sta: updates require a relaunch to take effect. In managed environments, push the update through your enterprise browser management (Chrome Browser Cloud Management / Group Policy) and enforce auto-update to avoid users lingering on vulnerable builds. Because this is a sandbox-escape that requires a prior renderer compromise, defense-in-depth against the first stage helps: enabling Chrome's Site Isolation (default) and keeping renderer/JS-engine components patched reduces the odds an attacker reaches the position needed to trigger this bug. No standalone non-patch workaround fully neutralizes the flaw, so upgrading is the definitive fix.