CVE-2026-7918

chromium-browser: Use after free in GPU

Published May 6, 2026 CVSS 3.1 · 8.3 High EPSS < 1% KEV · Not listed
Description
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: High)

Analysis

AI-generated

Technical impact

The vulnerability is a use‑after‑free in the graphics pipeline of Chrome prior to version 148.0.7778.96, which can be triggered by a crafted HTML page. This flaw arises from improper memory handling in the GPU component and is identified by CWE‑416 and CWE‑825. If an attacker can compromise the renderer process through the web content, the defect may allow the process to escape its sandbox, potentially leading to execution of arbitrary code on the host system.

Affected Systems

All desktop builds of Chrome older than 148.0.7778.96 on any operating system are affected because the GPU code is shared across platforms. Users must verify and apply the most recent Chrome release or an equivalent security update.

Risk and Exploitability

The CVSS score of 8.3 indicates a high severity impact if exploited. However, the EPSS score of less than 1% suggests that current exploitation probability is low, likely due to the need for a renderer process compromise that is not yet widespread. The CVE is not listed in the CISA KEV catalog, meaning no publicly known exploits have been documented yet. Based on the description, the likely attack vector is a malicious website or compromised extension that delivers a crafted page, which would trigger the use‑after‑free. The threat therefore remains significant but with a modest current exploitation likelihood.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the latest Chrome update that includes version 148.0.7778.96 or newer to remove the GPU use‑after‑free flaw.
  • If a patch cannot be applied immediately, start Chrome with the --disable-gpu flag or otherwise disable hardware acceleration to bypass the vulnerable code path.
  • Run Chrome in a container or otherwise isolate it with strict sandboxing settings so that even if a process escape occurs, the impact on the host system is limited.

Generated by OpenCVE AI on May 9, 2026 at 04:19 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DSA Debian DSA DSA-6250-1 chromium security update
History
Type Values Removed Values Added
Title chromium-browser: Use after free in GPU
Weaknesses CWE-825
References
Metrics threat_severity

None

threat_severity

Important

Type Values Removed Values Added
Title GPU Use‑After‑Free Leading to Sandbox Escape in Chrome Before 148.0.7778.96
Type Values Removed Values Added
First Time appeared Apple
Apple macos
Linux
Linux linux Kernel
Microsoft
Microsoft windows
CPEs cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*
cpe:2.3:o:apple:macos:-:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:*
cpe:2.3:o:microsoft:windows:-:*:*:*:*:*:*:*
Vendors & Products Apple
Apple macos
Linux
Linux linux Kernel
Microsoft
Microsoft windows
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 8.3, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H'}

Type Values Removed Values Added
Title GPU Use‑After‑Free Leading to Sandbox Escape in Chrome Before 148.0.7778.96
Type Values Removed Values Added
First Time appeared Google
Google chrome
Vendors & Products Google
Google chrome
Type Values Removed Values Added
Description 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: High)
Weaknesses CWE-416
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Chrome
Published
Updated
May 7, 2026, 3:56 AM
Reserved
May 5, 2026, 10:59 PM
Status
Analyzed
Published
May 6, 2026, 7:16 PM
Modified
Oct 26, 2026, 7:10 PM
Severity
Important
Public date
May 5, 2026, 12:00 AM