CVE-2026-76022

Received Received - Intake

Buffer Overflow in Google Chrome Prior to 151.0.7922.173

Publication date: 2026-08-20

Last updated on: 2026-08-20

Assigner: Chrome

Description

Buffer overflow in Network in Google Chrome prior to 151.0.7922.173 allowed a remote attacker to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-08-20

Last Modified

2026-08-20

Generated

2026-08-21

AI Q&A

2026-08-21

EPSS Evaluated

N/A

NVD

CVE-2026-76022

EUVD

EUVD-2026-63599

Affected Vendors & Products

Vendor	Product	Version / Range
google	chrome	to 151.0.7922.173 (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 Network component. It allows a remote attacker to execute arbitrary code outside the sandbox by tricking a user into visiting a specially crafted HTML page. The vulnerability exists in Chrome versions prior to 151.0.7922.173.

Impact Analysis

An attacker could exploit this to run malicious code on your device, potentially stealing data, installing malware, or taking control of your system. Since it bypasses the sandbox, it has elevated privileges compared to normal web content.

Mitigation Strategies

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

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

0/70