Heap Buffer Overflow in Google Chrome

Publication date: 2026-05-28

Last updated on: 2026-06-01

Assigner: Chrome

Description

Heap buffer overflow in ANGLE in Google Chrome prior to 148.0.7778.216 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-05-28

Last Modified

2026-06-01

Generated

2026-07-09

AI Q&A

2026-05-29

EPSS Evaluated

2026-07-08

NVD

CVE-2026-9940

EUVD

EUVD-2026-33082

Affected Vendors & Products

Vendor	Product	Version / Range
google	chrome	to 148.0.7778.216 (exc)

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

Executive Summary

This vulnerability is a heap buffer overflow in ANGLE, a component used in Google Chrome. It occurs in versions of Chrome prior to 148.0.7778.216 and allows a remote attacker to potentially exploit heap corruption by using a specially crafted HTML page.

Impact Analysis

The vulnerability can lead to heap corruption, which may allow a remote attacker to execute arbitrary code or cause a denial of service in the affected version of Google Chrome.

Hi! I’m here to help you understand CVE-2026-9940. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70