Heap Buffer Overflow in Google Chrome WebNN on Windows

Publication date: 2026-06-30

Last updated on: 2026-07-02

Assigner: Chrome

Description

Heap buffer overflow in WebNN in Google Chrome on Windows prior to 150.0.7871.47 allowed a remote attacker who had compromised the renderer process to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Low)

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-06-30

Last Modified

2026-07-02

Generated

2026-07-21

AI Q&A

2026-07-01

EPSS Evaluated

2026-07-19

NVD

CVE-2026-14087

EUVD

EUVD-2026-40774

Affected Vendors & Products

Vendor	Product	Version / Range
google	chrome	to 150.0.7871.47 (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().
CWE-20	The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
CWE-787	The product writes data past the end, or before the beginning, of the intended buffer.

Attack-Flow Graph

Executive Summary

This vulnerability is a heap buffer overflow in the WebNN component of Google Chrome on Windows versions prior to 150.0.7871.47. It allows a remote attacker, who has already compromised the renderer process, to potentially exploit heap corruption by using a specially crafted HTML page.

Impact Analysis

If exploited, this vulnerability could allow an attacker to cause heap corruption, which might lead to unexpected behavior such as crashes or potentially executing arbitrary code within the renderer process. However, the severity is classified as low.

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

0/70