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

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

Google Chrome versions prior to 148.0.7778.96 contain a sandbox escape vulnerability in the GPU component that allows attackers who have compromised the renderer process to escalate privileges and…. A patch is available.

How to fix or mitigate CVE-2026-7985?

Within 24 hours: Verify current Chrome deployment version across your fleet using mobile device management (MDM) or enterprise patch management tools. Within 7 days: Deploy Chrome version 148.0.7778.96 or later through your standard patch management process to all Chrome installations; prioritize systems in high-risk roles (developers, security teams, finance). Within 30 days: Audit logs for any suspicious GPU process activity or unexpected privilege escalations; validate 100% deployment completion and confirm no systems remain on versions prior to 148.0.7778.96.

Google Chrome CVE-2026-7985

EUVD-2026-28073 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:33 vuln.today

CVSS changed

May 06, 2026 - 22:22 NVD

8.3 (HIGH)

CVE Published

May 06, 2026 - 18:13 nvd

HIGH 8.3

DescriptionCVE.org

Use after free in GPU 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's GPU component affects versions prior to 148.0.7778.96. An attacker who has already compromised the renderer process can escalate privileges to break out of Chrome's sandbox by exploiting a use-after-free memory corruption vulnerability via a specially crafted HTML page. This requires high attack complexity and user interaction (visiting a malicious page). No active exploitation confirmed at time of analysis, and vendor-released patch (version 148.0.7778.96) is available. EPSS data not provided, but the combination of network vector, changed scope (S:C in CVSS), and sandbox escape capability makes this a priority update for Chrome deployments despite Chromium's 'Medium' internal severity rating.

Technical ContextAI

This vulnerability stems from a use-after-free condition (CWE-416) in Chrome's GPU process implementation. Use-after-free occurs when code continues to use a memory pointer after the memory has been freed, potentially allowing attackers to control the freed memory's contents and redirect program execution. Chrome employs a multi-process sandbox architecture where the renderer process (handling web content) runs with restricted privileges, isolated from the GPU process. The GPU process manages graphics rendering operations and has elevated system access compared to renderers. The CVSS scope change metric (S:C) indicates this vulnerability allows escape from the renderer's security boundary into the GPU process context, representing a privilege escalation across Chrome's security architecture. Affected product per CPE: cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:* covering all Chrome versions below 148.0.7778.96.

RemediationAI

Update Google Chrome to version 148.0.7778.96 or later immediately, as confirmed by Google's stable channel update announcement at chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop.html. Chrome typically auto-updates within 24-48 hours; administrators should verify update deployment via chrome://settings/help or enterprise management consoles. For environments requiring manual updates, download version 148.0.7778.96+ from official Google Chrome distribution channels. If immediate patching is not feasible, implement compensating controls: disable GPU process acceleration via --disable-gpu command-line flag (trade-off: significant performance degradation for graphics-intensive web applications and video playback; may break WebGL/WebGPU content); restrict browsing to trusted sites only via enterprise policy controls; deploy browser isolation solutions that contain rendering in cloud/sandbox environments. Note that disabling GPU acceleration fundamentally changes Chrome's architecture and may cause compatibility issues with modern web applications. No workaround fully mitigates the sandbox escape risk - patching to 148.0.7778.96 remains the only complete remediation.