CVE-2026-9924
Undergoing Analysis Undergoing Analysis - In Progress
Heap Buffer Overflow in Google Chrome on Windows

Publication date: 2026-05-28

Last updated on: 2026-05-29

Assigner: Chrome

Description
Heap buffer overflow in ANGLE in Google Chrome on Windows 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
Published
2026-05-28
Last Modified
2026-05-29
Generated
2026-05-29
AI Q&A
2026-05-29
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
google chrome to 148.0.7778.216 (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 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 on Windows versions prior to 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 sandbox environment that normally restricts the renderer process. This could lead to the attacker gaining higher privileges on the affected system, potentially allowing them to execute arbitrary code or perform unauthorized actions beyond the browser.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart