CVE-2026-9915
Undergoing Analysis
Undergoing Analysis - In Progress
Heap Buffer Overflow in Google Chrome
Publication date: 2026-05-28
Last updated on: 2026-05-29
Assigner: Chrome
Description
Description
Heap buffer overflow in ANGLE in Google Chrome prior to 148.0.7778.216 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)
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| chrome | 148.0.7778.216 |
Helpful Resources
Exploitability
CWE
KEV
| 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 Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a heap buffer overflow in ANGLE, a component used in Google Chrome before version 148.0.7778.216. 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.
How can this vulnerability impact me? :
If exploited, this vulnerability could allow an attacker to break out of the browser's sandbox environment, potentially gaining higher privileges on the affected system. This could lead to unauthorized access, data theft, or further system compromise.
Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70