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

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

Google Chrome versions prior to 148.0.7778.96 contain a sandbox escape vulnerability that allows attackers with renderer process access to achieve complete system compromise.. A patch is available.

How to fix or mitigate CVE-2026-7967?

Within 24 hours: Verify current Chrome deployment versions across all endpoints using your endpoint management platform and identify systems running versions before 148.0.7778.96. Within 7 days: Deploy Chrome 148.0.7778.96 or later to all enterprise devices via your software distribution mechanism (Google Update, WSUS, or MDM). Within 30 days: Audit and document patch compliance; review renderer process isolation policies and consider restricting Chrome usage on high-risk systems pending full patch deployment.

Google Chrome CVE-2026-7967

EUVD-2026-28037 HIGH

Improper Input Validation (CWE-20)

2026-05-06 Chrome

Information Disclosure Google 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:30 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

Insufficient validation of untrusted input in Navigation 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 attackers who have already compromised the renderer process to break out of Chrome's security sandbox through malicious HTML pages. The vulnerability stems from insufficient input validation in Chrome's Navigation component, requiring both network access and user interaction but enabling complete system compromise (high confidentiality, integrity, and availability impact) once the renderer is compromised. Vendor-released patch available in version 148.0.7778.96, announced via Google's stable channel update.

Technical ContextAI

This vulnerability affects the Navigation component in Google Chrome's multi-process architecture. Chrome employs process sandboxing as a critical security boundary where the renderer process (which parses and executes web content) runs with restricted privileges. The CWE-20 (Improper Input Validation) classification indicates Chrome failed to adequately validate untrusted input during navigation operations, creating an escape vector from the renderer sandbox. The CVSS vector shows Scope Change (S:C), confirming the vulnerability crosses security boundaries from the sandboxed renderer to the broader system. This represents a two-stage attack where an initial renderer compromise (typically via a separate vulnerability) is escalated to full sandbox escape. The CPE identifier cpe:2.3:a:google:chrome confirms this affects the Google Chrome application across all platforms where the browser is deployed.

RemediationAI

Update Google Chrome to version 148.0.7778.96 or later immediately via Chrome's built-in updater (chrome://settings/help will check and apply updates automatically) or through enterprise deployment tools for managed environments. Google's stable channel update from May 2026 includes the fix, available at chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop.html. For enterprise environments unable to patch immediately, implement compensating controls: restrict Chrome usage to trusted websites only via URL filtering policies, enforce Chrome Enterprise policy to disable automatic renderer process reuse (IsolateOrigins policy), and enable Enhanced Safe Browsing mode to reduce renderer compromise risk from initial exploit chains. Note that Enhanced Safe Browsing sends additional browsing data to Google for analysis. These workarounds reduce but do not eliminate risk, as sophisticated attackers may still chain exploits. Organizations using Chromium-based browsers (Microsoft Edge, Brave, Vivaldi) should verify their vendors have incorporated this upstream Chromium fix.