CVE-2026-12010
Received Received - Intake
Heap Buffer Overflow in Google Chrome Android GPU

Publication date: 2026-06-11

Last updated on: 2026-06-11

Assigner: Chrome

Description
Heap buffer overflow in GPU in Google Chrome on Android prior to 149.0.7827.115 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)
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-11
Last Modified
2026-06-11
Generated
2026-06-12
AI Q&A
2026-06-12
EPSS Evaluated
N/A
NVD
CVE-2026-12010
EUVD
EUVD-2026-36331
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
google chrome to 149.0.7827.115 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-122 A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Impact Analysis

If exploited, this vulnerability could allow an attacker to break out of the browser's sandbox environment, potentially gaining higher privileges on the affected device. This could lead to unauthorized access to sensitive data or control over the device.

Executive Summary

This vulnerability is a heap buffer overflow in the GPU component of Google Chrome on Android versions prior to 149.0.7827.115. It allows a remote attacker, who has already compromised the renderer process, to potentially escape the browser's sandbox by using a specially crafted HTML page.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-12010. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart