CVE-2026-10898

chromium-browser: Stack buffer overflow in GPU

Published Jun 4, 2026 CVSS 3.1 · 8.3 High EPSS < 1% KEV · Not listed
Description
Stack buffer overflow in GPU in Google Chrome prior to 149.0.7827.53 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Critical)

Analysis

AI-generated

Technical impact

A stack buffer overflow in the GPU component of Google Chrome allows a remote attacker who has already compromised the renderer process to perform a sandbox escape. The overflow is triggered by a crafted HTML page, giving the attacker the potential to escape the renderer sandbox and execute code in a higher privilege context within the browser process. The weakness is a classic stack‑based buffer overflow, identified as both CWE‑120 and CWE‑121.

Affected Systems

Google Chrome desktop builds prior to version 149.0.7827.53 on all platforms that include the GPU process. Users running any older stable channel release are affected and should upgrade to the latest available build.

Risk and Exploitability

Chromium security severity is listed as Critical. The EPSS score is <1% and the vulnerability is not in CISA KEV. The exploit would require first delivering a malicious HTML page that loads in a compromised renderer. The likely attack vector is a user visiting or interacting with a malicious website, permitting the overflow to occur. Given the severity and the need for advanced exploitation knowledge, the risk is high for systems that cannot apply the patch promptly. The CVSS score of 8.3 indicates a high severity level.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Install the latest Google Chrome update, version 149.0.7827.53 or newer.
  • If an update cannot be applied immediately, disable GPU usage by starting Chrome with the flag --disable-gpu to eliminate the vulnerable code path.
  • Configure enterprise policy to block execution of untrusted renderer content or to enforce strict site isolation to reduce the impact of any remaining gadgets.

Generated by OpenCVE AI on June 7, 2026 at 14:05 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DSA Debian DSA DSA-6325-1 chromium security update
History
Type Values Removed Values Added
Title GPU Stack Buffer Overflow Enabling Sandbox Escape in Google Chrome chromium-browser: Stack buffer overflow in GPU
Weaknesses CWE-120
References
Metrics threat_severity

None

threat_severity

Important

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
Title GPU Stack Buffer Overflow Enabling Sandbox Escape in Google Chrome
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
First Time appeared Google
Google chrome
Vendors & Products Google
Google chrome
Type Values Removed Values Added
Description Stack buffer overflow in GPU in Google Chrome prior to 149.0.7827.53 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Critical)
Weaknesses CWE-121
References
Weaknesses
  • CWE-120

    Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

  • CWE-121

    Stack-based Buffer Overflow

Sources

Status
PUBLISHED
Assigner
Chrome
Published
Updated
Jun 5, 2026, 1:43 AM
Reserved
Jun 4, 2026, 5:05 PM
Status
Analyzed
Published
Jun 4, 2026, 11:16 PM
Modified
Jul 22, 2026, 8:10 PM
Severity
Important
Public date
Jun 2, 2026, 12:00 AM