CVE-2026-7900
Awaiting Analysis Awaiting Analysis - Queue
Heap Buffer Overflow in Google Chrome

Publication date: 2026-05-06

Last updated on: 2026-05-06

Assigner: Chrome

Description
Heap buffer overflow in ANGLE in Google Chrome prior to 148.0.7778.96 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-06
Last Modified
2026-05-06
Generated
2026-06-16
AI Q&A
2026-05-06
EPSS Evaluated
2026-06-14
NVD
CVE-2026-7900
EUVD
EUVD-2026-27903
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
google chrome to 148.0.7778.96 (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
Executive Summary

This vulnerability is a heap buffer overflow in ANGLE within Google Chrome versions prior to 148.0.7778.96. 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.

Impact Analysis

If exploited, this vulnerability could allow an attacker to break out of the sandbox environment that normally restricts the browser's capabilities. This could lead to unauthorized access to the underlying system, potentially allowing the attacker to execute arbitrary code or gain higher privileges.

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