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

CVE-2026-7970 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.1%.

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

Google Chrome versions before 148.0.7778.96 contain a sandbox escape vulnerability (CVE-2026-7970, CVSS 8.3) that could allow attackers to elevate privileges from a compromised renderer process to…. A patch is available.

How to fix or mitigate CVE-2026-7970?

Within 24 hours: Verify your organization's current Chrome deployment version across all endpoints using your mobile device management (MDM) or endpoint management solution. Within 7 days: Deploy Chrome 148.0.7778.96 or later to all devices via your standard patch management process, prioritizing systems with high-risk user profiles (finance, HR, executive staff). Within 30 days: Confirm 95%+ patch compliance through automated scanning and audit logs; flag any systems running versions prior to 148.0.7778.96 for manual remediation or decommissioning.

Google Chrome CVE-2026-7970

EUVD-2026-28043 HIGH

Use After Free (CWE-416)

2026-05-06 Chrome

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

8.3

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

8.3 HIGH

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

SUSE

HIGH

qualitative

Red Hat

9.0 MEDIUM

qualitative

Primary rating from NVD.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

High

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

May 06, 2026 - 22:31 vuln.today

CVSS changed

May 06, 2026 - 22:22 NVD

8.3 (HIGH)

CVE Published

May 06, 2026 - 18:12 nvd

HIGH 8.3

DescriptionCVE.org

Use after free in TopChrome in Google Chrome prior to 148.0.7778.96 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Medium)

AnalysisAI

Sandbox escape in Google Chrome versions prior to 148.0.7778.96 allows remote attackers who have already compromised the renderer process to break out of Chrome's security sandbox through a use-after-free vulnerability in the TopChrome component. Attack requires user interaction with a malicious HTML page and has high attack complexity. EPSS data not available; no active exploitation confirmed at time of analysis. Vendor-released patch available in Chrome 148.0.7778.96.

Technical ContextAI

This vulnerability involves a use-after-free (CWE-416) memory corruption issue in TopChrome, Chrome's UI framework component that manages browser-level interface elements like the address bar and tabs. Use-after-free vulnerabilities occur when code continues to use a memory pointer after the memory has been freed, allowing attackers to manipulate memory allocation and potentially execute arbitrary code. In Chromium's multi-process architecture, the renderer process runs web content in a restricted sandbox. The CVSS scope change (S:C) indicates this vulnerability enables escape from that sandbox boundary into the browser process, which has elevated privileges. This represents a critical architectural security boundary breach in Chrome's defense-in-depth model.

RemediationAI

Immediately update Google Chrome to version 148.0.7778.96 or later via Chrome's built-in automatic update mechanism (Settings → About Chrome) or by downloading from google.com/chrome. The vendor advisory is available at chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop.html with technical details at issues.chromium.org/issues/497487462. For enterprise deployments unable to patch immediately, compensating controls include enforcing Chrome Enterprise policies to disable JavaScript on untrusted sites (blocks renderer exploitation vector but severely impacts functionality), implementing network-level content filtering to block known malicious domains, and using application sandboxing tools like Windows Defender Application Guard to add additional isolation layers beyond Chrome's built-in sandbox. These mitigations carry significant usability trade-offs and should be considered temporary until patching is completed. No workaround fully addresses the vulnerability without the vendor patch.