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

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

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

Google Chrome versions prior to 148.0.7778.96 contain a critical sandbox escape vulnerability that allows remote attackers to execute arbitrary code on user systems through a malicious webpage visit…. A patch is available.

How to fix or mitigate CVE-2026-7908?

Within 24 hours: Audit Chrome versions in use across endpoints using asset management tools and identify all systems running versions prior to 148.0.7778.96. Within 7 days: Deploy Chrome 148.0.7778.96 or later to all user endpoints via your standard patch management process; configure auto-update policies to enforce this version minimum. Within 30 days: Verify 100% compliance through vulnerability scanning and audit logs confirming all Chrome instances are at patched version or newer.

Google Chrome CVE-2026-7908

EUVD-2026-27919 CRITICAL

Use After Free (CWE-416)

2026-05-06 Chrome

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

9.6

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

9.6 CRITICAL

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

SUSE

CRITICAL

qualitative

Red Hat

9.6 HIGH

qualitative

Primary rating from NVD.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

May 06, 2026 - 22:24 vuln.today

CVSS changed

May 06, 2026 - 22:22 NVD

9.6 (CRITICAL)

CVE Published

May 06, 2026 - 18:12 nvd

CRITICAL 9.6

DescriptionCVE.org

Use after free in Fullscreen in Google Chrome prior to 148.0.7778.96 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)

AnalysisAI

Sandbox escape in Google Chrome versions prior to 148.0.7778.96 allows remote attackers to break out of the browser's security sandbox through a use-after-free vulnerability in the Fullscreen API component. Attackers can deliver exploitation via a specially crafted HTML page requiring only user visit to the page (no additional interaction). With CVSS 9.6 (Critical) and scope change indicating containment breach, this represents a serious risk to browser security model integrity. No evidence of active exploitation (not in CISA KEV) and EPSS data not available at time of analysis.

Technical ContextAI

This is a use-after-free (CWE-416) memory corruption vulnerability in Chrome's Fullscreen API implementation. Use-after-free bugs occur when code continues to use a memory pointer after the memory has been freed, allowing attackers to manipulate the freed memory region and potentially achieve arbitrary code execution. The vulnerability exists in the fullscreen handling component which manages transitions between normal and fullscreen display modes. According to the CPE string cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*, all Chrome versions before 148.0.7778.96 across all platforms (Windows, macOS, Linux) are affected. The Chromium security severity rating of 'High' combined with sandbox escape capability indicates this vulnerability can bypass Chrome's multi-process architecture and sandboxing protections that normally isolate web content from the underlying operating system.

RemediationAI

Update Google Chrome to version 148.0.7778.96 or later immediately. Chrome typically auto-updates within hours to days for most users; administrators should verify update deployment across managed fleets using chrome://settings/help to check version or enterprise update policies. Desktop users can manually trigger updates via Menu > Help > About Google Chrome. Enterprise environments using Google Chrome Browser Cloud Management or Group Policy should push version 148.0.7778.96+ through existing update channels. Consult official vendor advisory at chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop.html for complete update instructions. If immediate patching is infeasible, consider temporary compensating controls: restrict user access to untrusted websites through web filtering/allowlisting (reduces exposure to malicious HTML pages but significantly impacts usability), deploy browser isolation solutions that render untrusted content in remote sandboxed environments (adds latency and infrastructure cost), or implement application allowlisting to prevent Chrome execution on critical systems until patched (severe operational impact). These mitigations provide only partial risk reduction and should not replace timely patching.