Skip to main content
CVE Vulnerability Database
Vulnerability Database/CVE-2026-14144

CVE-2026-14144: Google Chrome XSS Vulnerability

CVE-2026-14144 is a cross-site scripting flaw in Google Chrome that enables UI spoofing attacks through malicious HTML pages. This article covers the technical details, affected versions, security impact, and mitigation.

Published:

CVE-2026-14144 Overview

CVE-2026-14144 is an incorrect security UI vulnerability in the Views component of Google Chrome. The flaw affects Chrome versions prior to 150.0.7871.47 across Windows, macOS, and Linux. A remote attacker who convinces a user to perform specific UI gestures can spoof security-relevant interface elements through a crafted HTML page. The issue is classified under CWE-451: User Interface (UI) Misrepresentation of Critical Information. Chromium rates the security severity as Low, and the CVSS score reflects high attack complexity combined with required user interaction.

Critical Impact

Attackers can misrepresent security indicators in the Chrome UI, enabling phishing and social engineering scenarios that trick users into trusting malicious content.

Affected Products

  • Google Chrome versions prior to 150.0.7871.47
  • Chrome on Microsoft Windows
  • Chrome on Apple macOS and Linux

Discovery Timeline

  • 2026-06-30 - CVE-2026-14144 published to NVD
  • 2026-07-01 - Last updated in NVD database

Technical Details for CVE-2026-14144

Vulnerability Analysis

The vulnerability resides in the Views subsystem of Chromium, which renders browser chrome elements such as dialogs, permission prompts, address bar overlays, and other security-relevant UI components. Incorrect handling of these Views allows attacker-controlled web content to overlap, mimic, or misrepresent trusted browser UI. Successful exploitation requires the victim to perform specific UI gestures on a crafted HTML page.

The attack does not compromise memory safety or execute arbitrary code. Instead, it undermines the integrity of security signals the user relies on to make trust decisions. This aligns with the [CWE-451] classification for misrepresenting critical information in the interface.

Root Cause

The root cause is improper enforcement of layering, focus, or origin boundaries in the Views component. When the browser fails to distinguish attacker-drawn content from legitimate chrome, the user cannot reliably identify which element originated from Chrome itself. This creates the conditions for spoofing security indicators.

Attack Vector

Exploitation requires network access and user interaction. The attacker hosts a crafted HTML page and lures the target to visit it, typically through phishing, malvertising, or a compromised site. The victim must then perform specific UI gestures such as clicks, drags, or focus changes for the spoofed UI to render convincingly. Because the required gesture sequence is non-trivial, attack complexity is high.

No verified public exploit or proof-of-concept code is available at the time of publication. Refer to the Chromium Issue Tracker Entry for technical details tracked by the vendor.

Detection Methods for CVE-2026-14144

Indicators of Compromise

  • Chrome browser processes running versions earlier than 150.0.7871.47 on managed endpoints.
  • Outbound web traffic to newly registered or low-reputation domains hosting HTML content that mimics browser security dialogs.
  • User reports of unexpected permission prompts, download dialogs, or address bar behavior on specific sites.

Detection Strategies

  • Inventory installed Chrome versions across the fleet using endpoint telemetry and flag hosts running vulnerable builds.
  • Correlate browser process telemetry with visits to suspicious domains that deliver HTML designed to overlap browser chrome.
  • Monitor phishing report queues for user-submitted screenshots showing anomalous Chrome UI elements.

Monitoring Recommendations

  • Ingest Chrome update and version telemetry into centralized logging to track patch compliance.
  • Alert on user-reported credential entry into sites reached from links inside crafted HTML pages.
  • Track proxy and DNS logs for domains serving pages that request unusual UI-driven gestures shortly after page load.

How to Mitigate CVE-2026-14144

Immediate Actions Required

  • Update Chrome to version 150.0.7871.47 or later on all Windows, macOS, and Linux endpoints.
  • Force restart of Chrome after update to ensure the patched binary is loaded.
  • Verify enterprise policy channels are configured to deliver Stable channel updates promptly.

Patch Information

Google addressed CVE-2026-14144 in the Chrome Stable channel release announced in the Google Chrome Stable Update. Administrators should confirm that Chrome version 150.0.7871.47 or newer is deployed. Additional context is available in the Chromium Issue Tracker Entry.

Workarounds

  • Enforce automatic Chrome updates through enterprise policy so users cannot defer patching.
  • Deliver user awareness guidance on identifying spoofed browser UI and reporting suspicious prompts.
  • Restrict access to untrusted sites through web filtering until patched builds are confirmed on all endpoints.

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Default Legacy - Prefooter | Experience the World’s Most Advanced Cybersecurity Platform

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.