Skip to main content

Google Chrome CVE-2026-8578

| EUVDEUVD-2026-30399 LOW
Out-of-bounds Read (CWE-125)
2026-05-14 Chrome GHSA-wxm5-8hjp-cm79
3.1
CVSS 3.1 · NVD

Severity by source

NVD PRIMARY
3.1 LOW
AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

Lifecycle Timeline

3
Analysis Generated
May 15, 2026 - 15:26 vuln.today
CVSS changed
May 15, 2026 - 15:22 NVD
3.1 (None) 3.1 (LOW)
CVE Published
May 14, 2026 - 19:52 nvd
UNKNOWN (no severity yet)

DescriptionCVE.org

Out of bounds read in GPU in Google Chrome on Linux prior to 148.0.7778.168 allowed a remote attacker who had compromised the renderer process to leak cross-origin data via a crafted HTML page. (Chromium security severity: Medium)

AnalysisAI

Google Chrome on Linux versions prior to 148.0.7778.168 suffers from an out-of-bounds read vulnerability in GPU processing that enables cross-origin data leakage. An attacker who has already compromised the renderer process can craft malicious HTML to read sensitive memory beyond allocated bounds, exposing data from other origins that should be isolated by the browser's same-origin policy. EPSS exploitation probability is very low (0.03%, 10th percentile) and no active exploitation or public POC has been identified. Google rates this Medium severity and released patch 148.0.7778.168 to address the issue.

Technical ContextAI

This vulnerability affects Google Chrome's GPU process on Linux platforms, specifically the graphics rendering pipeline that handles HTML content. CWE-125 (Out-of-bounds Read) indicates the code attempts to read memory outside allocated buffer boundaries during GPU operations. Modern browsers use multi-process architectures where the renderer process handles page content in a sandboxed environment separate from the browser core. The GPU process performs hardware-accelerated graphics operations and sits between renderer and system GPU drivers. An out-of-bounds read in this component allows attackers who have already escaped renderer sandbox constraints (via a separate compromise) to leak memory contents that may include cross-origin data - violating the Same-Origin Policy that prevents scripts from one domain accessing data from another. The Linux-specific nature suggests the vulnerability involves platform-specific GPU driver interfaces or memory management patterns not present in Chrome's Windows or macOS implementations.

RemediationAI

Update Google Chrome on Linux to version 148.0.7778.168 or later immediately. Chrome's built-in auto-update mechanism should apply this patch automatically for most users - verify by navigating to chrome://settings/help and confirming version number is 148.0.7778.168 or higher. For enterprise deployments using managed Chrome installations, push the update through your software distribution system. The official advisory is available at http://chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop_12.html. No workarounds are available as this is a core GPU processing flaw. If immediate patching is not possible, consider these compensating controls with trade-offs: disabling GPU acceleration via chrome://flags/#disable-accelerated-video-decode reduces attack surface but significantly degrades rendering performance and user experience, particularly for video and graphics-intensive web applications. Restricting user access to untrusted websites through web filtering reduces exposure to malicious HTML but does not address the underlying vulnerability and may impact legitimate business functions. These mitigations are temporary only - patching remains the only complete remediation.

More in Chrome

View all
CVE-2015-5122 CRITICAL POC
9.8 Jul 14

Use-after-free vulnerability in the DisplayObject class in the ActionScript 3 (AS3) implementation in Adobe Flash Player

CVE-2016-5198 HIGH POC
8.8 Jan 19

V8 in Google Chrome prior to 54.0.2840.90 for Linux, and 54.0.2840.85 for Android, and 54.0.2840.87 for Windows and Mac

CVE-2017-5070 HIGH POC
8.8 Oct 27

Type confusion in V8 in Google Chrome prior to 59.0.3071.86 for Linux, Windows, and Mac, and 59.0.3071.92 for Android, a

CVE-2016-1646 HIGH POC
8.8 Mar 29

The Array.prototype.concat implementation in builtins.cc in Google V8, as used in Google Chrome before 49.0.2623.108, do

CVE-2013-0758 CRITICAL POC
9.3 Jan 13

Mozilla Firefox before 18.0, Firefox ESR 10.x before 10.0.12 and 17.x before 17.0.2, Thunderbird before 17.0.2, Thunderb

CVE-2017-5030 HIGH POC
8.8 Apr 24

Incorrect handling of complex species in V8 in Google Chrome prior to 57.0.2987.98 for Linux, Windows, and Mac and 57.0.

CVE-2012-3993 CRITICAL POC
9.3 Oct 10

The Chrome Object Wrapper (COW) implementation in Mozilla Firefox before 16.0, Firefox ESR 10.x before 10.0.8, Thunderbi

CVE-2017-3823 HIGH POC
8.8 Feb 01

An issue was discovered in the Cisco WebEx Extension before 1.0.7 on Google Chrome, the ActiveTouch General Plugin Conta

CVE-2014-8636 HIGH POC
7.5 Jan 14

The XrayWrapper implementation in Mozilla Firefox before 35.0 and SeaMonkey before 2.32 does not properly interact with

CVE-2013-0757 CRITICAL POC
9.3 Jan 13

The Chrome Object Wrapper (COW) implementation in Mozilla Firefox before 18.0, Firefox ESR 17.x before 17.0.2, Thunderbi

CVE-2014-1510 CRITICAL POC
9.8 Mar 19

The Web IDL implementation in Mozilla Firefox before 28.0, Firefox ESR 24.x before 24.4, Thunderbird before 24.4, and Se

CVE-2015-5123 CRITICAL
9.8 Jul 14

Use-after-free vulnerability in the BitmapData class in the ActionScript 3 (AS3) implementation in Adobe Flash Player 13

Share

CVE-2026-8578 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy