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

CVE-2026-17708 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-17708?

Google Chrome versions prior to 151.0.7922.72 contain a critical sandbox escape vulnerability (CVE-2026-17708, CVSS 9.6) that allows attackers with renderer-level code execution to elevate privileges…. A patch is available.

How to fix or mitigate CVE-2026-17708?

Within 24 hours, inventory Chrome desktop installations and identify systems in high-risk environments (security teams, executives, systems accessing sensitive data). Within 7 days, deploy Chrome 151.0.7922.72 or later across all desktop installations using enterprise deployment methods (Google Admin Console, Microsoft Intune, or configuration management tools) with mandatory enforcement. Within 30 days, validate patch deployment completeness through inventory audits and browser version reporting to confirm no vulnerable instances remain active.

Google Chrome CVE-2026-17708

EUVD-2026-50834 CRITICAL

Use After Free (CWE-416)

2026-07-30 Chrome

GHSA-6946-9r36-jh5w

Denial Of Service Google Use After Free Memory Corruption

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.0 HIGH

Requires a pre-compromised renderer foothold (PR:L) and reliable memory-reclamation plus victim navigation (AC:H, UI:R); success escapes the sandbox across a privilege boundary (S:C) with total impact.

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

4.0 AV:N/AC:H/AT:P/PR:L/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:30 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:18 cve.org

UNKNOWN (no severity yet)

CVE Published

Jul 30, 2026 - 00:18 cve.org

CRITICAL 9.6

DescriptionCVE.org

Use after free in Audio in Google Chrome 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 desktop prior to 151.0.7922.72 lets an attacker who has already compromised the renderer process leverage a use-after-free in the Audio component to break out of the sandbox via a crafted HTML page. Rated High by Chromium and CVSS 9.6 due to scope change, this is a second-stage exploit primitive rather than an initial-access bug; no public exploit has been identified at time of analysis and EPSS is low at 0.29%. A vendor patch is available in Chrome 151.0.7922.72.

Technical ContextAI

The flaw is a CWE-416 use-after-free in Chrome's Audio subsystem, the code path that handles audio rendering/streaming between the sandboxed renderer and the browser process. Use-after-free occurs when memory is freed but a dangling pointer is later dereferenced, allowing an attacker to control the reused allocation and corrupt object state. Because the Audio service interacts across Chromium's multi-process privilege boundary, corrupting it from a compromised renderer can yield code execution at a higher-privilege level, hence the CVSS Scope:Changed (S:C). The single CPE cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:* confirms Google Chrome (all channels prior to the fix) as the affected product; the reused Chromium engine means Chromium-derived browsers may share the underlying code but are not enumerated in this record.

RemediationAI

Vendor-released patch: Chrome 151.0.7922.72 - update Google Chrome to 151.0.7922.72 or later on Windows, macOS, and Linux and fully relaunch the browser so the new binaries load (Chrome auto-updates but requires a restart to complete). Verify via chrome://settings/help and, in managed fleets, push the update through your enterprise update policy or MDM rather than relying on per-user restarts. There is no practical feature-level workaround for a renderer-to-browser sandbox escape since it lives in the Audio path exercised by ordinary web content; as an interim compensating control for high-risk endpoints, restrict browsing to trusted sites and enforce prompt update rollout, accepting that these do not neutralize the underlying bug. Users of other Chromium-based browsers should apply their vendor's build that incorporates the corresponding Chromium fix. Advisory: https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html.