What is the CVSS score of EUVD-2026-50796?

EUVD-2026-50796 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 EUVD-2026-50796?

Google Chrome (desktop) versions prior to 151.0.7922.72 contain a use-after-free vulnerability in the Views UI framework allowing remote attackers to escape the browser sandbox if the renderer…. A patch is available.

How to fix or mitigate EUVD-2026-50796?

Within 24 hours, communicate the critical Chrome CVE-2026-17670 vulnerability and patch availability to end users and IT teams, enabling or enforcing automatic browser updates if not already active. Within 7 days, deploy Google Chrome version 151.0.7922.72 or later across your enterprise desktop fleet using standard patch management tools, prioritizing systems handling sensitive data or exposed to external networks. Within 30 days, verify patch deployment through browser telemetry and endpoint management systems to confirm all instances have reached the fixed version, and provide targeted security awareness training on multi-stage attack chains this vulnerability enables.

Google Chrome EUVD-2026-50796

| CVE-2026-17670 CRITICAL

Use After Free (CWE-416)

2026-07-30 Chrome

GHSA-qfg6-74c9-5pcg

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

Full sandbox escape gives scope change and total C/I/A, but the description's required prior renderer compromise plus heap grooming justifies AC:H rather than AC:L.

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

8.2 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 - 19:57 vuln.today

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 Views 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 versions prior to 151.0.7922.72 stems from a use-after-free in the Views UI framework, letting a remote attacker who has already compromised the renderer process break out of the sandbox via a crafted HTML page. Rated High by Chromium with a CVSS 9.6 due to scope change and total confidentiality/integrity/availability impact, though there is no public exploit identified at time of analysis and CISA SSVC records exploitation status as none. EPSS is low (0.29%, 21st percentile), consistent with a second-stage bug that requires prior renderer compromise rather than a directly weaponizable entry point.

Technical ContextAI

The flaw is a CWE-416 use-after-free in Chrome's Views framework - the C++ UI toolkit that renders and manages browser window widgets, menus, and controls in the privileged browser process. Use-after-free arises when an object is freed but a dangling pointer is later dereferenced, allowing an attacker who controls heap layout to reclaim the freed memory and steer execution or corrupt state. Because Views executes in the higher-privileged browser process rather than the sandboxed renderer, a UAF here is a classic sandbox-escape primitive: a compromised renderer sends crafted IPC/UI interactions that trigger the dangling reference in the browser process. The affected CPE is cpe:2.3:a:google:chrome (all versions up to the fix), and the tag set (Use After Free, Memory Corruption, Denial Of Service) reflects both control-flow-hijack and crash outcomes typical of this bug class.

RemediationAI

Vendor-released patch: update Google Chrome to 151.0.7922.72 or later on the Stable desktop channel, per the Chrome Releases advisory (https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html); most installations auto-update, so verify via chrome://settings/help and relaunch to apply. There is no supported in-product workaround for a memory-corruption bug, but because exploitation requires a compromised renderer as the first stage, defenders can reduce the entry-surface by keeping site isolation enabled (default), deploying enterprise policies to enforce timely updates, and restricting untrusted-site browsing; these lower the odds of the renderer compromise that precedes this escape but do not remediate the underlying UAF. Downstream Chromium-based browsers should be updated to the build that incorporates the equivalent Chromium fix (Chromium issue 513228974).