Heap Buffer Overflow in Google Chrome CrashReporting

Publication date: 2026-08-06

Last updated on: 2026-08-06

Assigner: Chrome

Description

Heap buffer overflow in CrashReporting in Google Chrome prior to 151.0.7922.109 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-08-06

Last Modified

2026-08-06

Generated

2026-08-07

AI Q&A

2026-08-07

EPSS Evaluated

N/A

NVD

CVE-2026-19138

Affected Vendors & Products

Vendor	Product	Version / Range
google	chrome	to 151.0.7922.109 (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 is a heap buffer overflow vulnerability in CrashReporting in Google Chrome before version 151.0.7922.109. A remote attacker who already compromised the renderer process could exploit this to potentially escape the sandbox via a specially crafted HTML page.

Impact Analysis

If you use an affected version of Chrome, an attacker who tricks you into visiting a malicious page could exploit this to run code outside the browser's sandbox. This could allow them to access your system more deeply than intended.

Mitigation Strategies

Update Google Chrome to version 151.0.7922.109 or later to address the heap buffer overflow in CrashReporting.

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

0/70