Heap Buffer Overflow in Chrome WebML Risks Data Exposure

Publication date: 2026-04-08

Last updated on: 2026-04-14

Assigner: Chrome

Description

Heap buffer overflow in WebML in Google Chrome prior to 147.0.7727.55 allowed a remote attacker to obtain potentially sensitive information from process memory via a crafted HTML page. (Chromium security severity: High)

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-04-08

Last Modified

2026-04-14

Generated

2026-07-06

AI Q&A

2026-04-09

EPSS Evaluated

2026-07-05

NVD

CVE-2026-5869

EUVD

EUVD-2026-20669

Affected Vendors & Products

Vendor	Product	Version / Range
google	chrome	to 147.0.7727.55 (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 the WebML component of Google Chrome versions prior to 147.0.7727.55. It allows a remote attacker to exploit a crafted HTML page to access potentially sensitive information from the process memory.

Impact Analysis

The impact of this vulnerability is that a remote attacker could obtain sensitive information from the memory of the Chrome process. This could lead to exposure of private data or other confidential information stored in the browser's memory.

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

0/70