CVE-2026-17924

Analyzed Analyzed - Analysis Complete

Use After Free in Google Chrome DNS Component

Publication date: 2026-07-30

Last updated on: 2026-08-03

Assigner: Chrome

Description

Use after free in DNS in Google Chrome prior to 151.0.7922.72 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Low)

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-07-30

Last Modified

2026-08-03

Generated

2026-08-19

AI Q&A

2026-07-30

EPSS Evaluated

2026-08-18

NVD

CVE-2026-17924

EUVD

EUVD-2026-50673

Affected Vendors & Products

Vendor	Product	Version / Range
google	chrome	to 151.0.7922.72 (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 the DNS component of Google Chrome versions before 151.0.7922.72. A use-after-free occurs when a program continues to use memory after it has been freed, potentially leading to crashes or arbitrary code execution. In this case, an attacker who compromised the renderer process could exploit this to escape the browser sandbox via a specially crafted HTML page.

Detection Guidance

This vulnerability is specific to Google Chrome versions prior to 151.0.7922.72. Detection involves checking the installed Chrome version. On Windows, run: wmic product where "name like 'Google Chrome'" get version. On Linux, run: google-chrome --version. If the version is below 151.0.7922.72, the system is vulnerable.

Impact Analysis

If you use an affected version of Google Chrome, this vulnerability could allow a remote attacker who already compromised the renderer process to escape the browser sandbox. This could enable the attacker to execute arbitrary code on your system with the same privileges as the browser, potentially leading to further compromise of your device or data.

Compliance Impact

This vulnerability does not directly impact compliance with GDPR, HIPAA, or similar standards as it involves a sandbox escape in Google Chrome. Compliance risks would depend on how the vulnerability is exploited in a specific environment, but no direct regulatory implications are described in the provided context.

Mitigation Strategies

Update Google Chrome to version 151.0.7922.72 or later to address the use after free vulnerability in DNS.

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

0/70