Use After Free in Google Chrome Renderer Process

Publication date: 2026-07-23

Last updated on: 2026-07-23

Assigner: Chrome

Description

Use after free in Input in Google Chrome prior to 150.0.7871.186 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-07-23

Last Modified

2026-07-23

Generated

2026-07-24

AI Q&A

2026-07-24

EPSS Evaluated

N/A

NVD

CVE-2026-16804

Affected Vendors & Products

Vendor	Product	Version / Range
google	chrome	to 150.0.7871.186 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-416	The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.

Attack-Flow Graph

Executive Summary

This vulnerability is a use-after-free issue in Google Chrome's Input component. It occurs when a program tries to use memory that has already been freed, potentially leading to unexpected behavior. In this case, an attacker who has already compromised the renderer process could exploit this to escape the browser's sandbox and execute arbitrary code on the system.

Impact Analysis

If you are using a vulnerable version of Google Chrome, an attacker could potentially take control of your computer by tricking you into visiting a specially crafted webpage. This could lead to data theft, installation of malware, or other malicious activities. Updating Chrome to version 150.0.7871.186 or later mitigates this risk.

Mitigation Strategies

Update Google Chrome to version 150.0.7871.186 or later to address the use after free vulnerability in Input that could lead to sandbox escape.

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

0/70