CVE-2026-15777
Analyzed Analyzed - Analysis Complete

Use After Free in Google Chrome UI on Linux

Vulnerability report for CVE-2026-15777, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-07-14

Last updated on: 2026-07-29

Assigner: Chrome

Description

Use after free in UI in Google Chrome on Linux prior to 150.0.7871.125 allowed a remote attacker who convinced a user to engage in specific UI gestures to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-14
Last Modified
2026-07-29
Generated
2026-08-04
AI Q&A
2026-07-15
EPSS Evaluated
2026-08-02
NVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
google chrome to 150.0.7871.125 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
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

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a use-after-free issue in the UI component of Google Chrome on Linux versions prior to 150.0.7871.125. A use-after-free vulnerability occurs when a program continues to use memory after it has been freed, which can lead to unexpected behavior or exploitation.

In this case, a remote attacker could exploit this flaw by convincing a user to perform specific UI gestures, such as clicking or interacting with elements on a crafted HTML page. Successful exploitation could result in heap corruption, which might allow the attacker to execute arbitrary code or cause other malicious impacts.

The Chromium security team has rated the severity of this vulnerability as High.

Detection Guidance

The provided context does not include specific detection methods or commands for identifying this vulnerability on a network or system. Detection would typically involve checking the installed version of Google Chrome on Linux systems to see if it is prior to 150.0.7871.125.

To check the version of Google Chrome on a Linux system, you can use the following command:

  • google-chrome --version

If the version is earlier than 150.0.7871.125, the system may be vulnerable.

Impact Analysis

If you are using an affected version of Google Chrome on Linux, this vulnerability could impact you in several ways:

  • An attacker could trick you into visiting a malicious website or interacting with a crafted HTML page, leading to potential exploitation.
  • Successful exploitation could result in heap corruption, which might allow the attacker to execute arbitrary code on your system.
  • This could lead to unauthorized access to your data, installation of malware, or other malicious activities on your device.
  • The attacker could gain control over your browser or system, potentially compromising sensitive information or performing actions on your behalf.
Compliance Impact

This vulnerability could impact compliance with common standards and regulations in the following ways:

  • GDPR (General Data Protection Regulation): If the vulnerability is exploited to access or exfiltrate personal data of EU citizens, it could lead to a data breach. Organizations are required to protect personal data under GDPR, and failure to do so could result in significant fines and legal consequences.
  • HIPAA (Health Insurance Portability and Accountability Act): For organizations handling protected health information (PHI), exploitation of this vulnerability could lead to unauthorized access to sensitive health data. This would constitute a breach under HIPAA, potentially resulting in penalties and mandatory breach notifications.
  • Other standards (e.g., PCI DSS, ISO 27001): If the vulnerability is exploited in systems processing payment card data or other sensitive information, it could violate requirements for securing systems and protecting data, leading to non-compliance and potential penalties.

Organizations should ensure they are using the patched version of Google Chrome to mitigate this vulnerability and maintain compliance with relevant regulations.

Mitigation Strategies

The immediate step to mitigate this vulnerability is to update Google Chrome to version 150.0.7871.125 or later. This version contains the fix for the use-after-free issue in the UI component.

  • Update Google Chrome using the package manager or download the latest version from the official Chrome website.

If updating is not immediately possible, consider the following temporary measures:

  • Avoid engaging with suspicious or untrusted web pages that may exploit this vulnerability.
  • Use alternative browsers that are not affected by this vulnerability until Chrome is updated.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-15777. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart