Buffer Overflow in Google Chrome

Publication date: 2026-08-25

Last updated on: 2026-08-25

Assigner: Chrome

Description

Buffer overflow in Media in Google Chrome prior to 152.0.7977.65 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: Medium)

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-08-25

Last Modified

2026-08-25

Generated

2026-08-26

AI Q&A

2026-08-26

EPSS Evaluated

N/A

NVD

CVE-2026-79231

Affected Vendors & Products

Vendor	Product	Version / Range
google	chrome	to 152.0.7977.65 (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 buffer overflow vulnerability in Google Chrome's Media component. It allows a remote attacker to execute arbitrary code within the browser's sandbox by tricking a user into visiting a specially crafted HTML page. The sandbox is designed to isolate processes for security, but this flaw bypasses those protections.

Impact Analysis

If exploited, this vulnerability could allow an attacker to run malicious code on your device. While the sandbox limits damage, it may still lead to data theft, installation of malware, or unauthorized system access. Users should update Chrome immediately to avoid exposure.

Mitigation Strategies

Update Google Chrome to version 152.0.7977.65 or later to address the buffer overflow vulnerability.

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

0/70