Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-106380 Overview
CVE-2026-106380 is a user interface misrepresentation vulnerability in Google Chrome prior to version 155.0.8059.39. A remote attacker can craft an HTML page that spoofs browser UI elements, enabling social engineering attacks against users who interact with the malicious page. The flaw is classified under CWE-451: User Interface (UI) Misrepresentation of Critical Information and was rated Low severity by the Chromium project. Google addressed the issue in a Stable Channel desktop update.
Critical Impact
Attackers can spoof trusted browser UI components through a crafted HTML page, deceiving users into disclosing credentials or approving unintended actions.
Affected Products
- Google Chrome Desktop (Windows, macOS, Linux) prior to 155.0.8059.39
- Chromium-based browsers inheriting the vulnerable UI rendering code
- Any application embedding affected Chromium builds
Discovery Timeline
- 2026-10-06 - CVE-2026-106380 published to the National Vulnerability Database (NVD)
- 2026-10-07 - Last updated in the NVD database
Technical Details for CVE-2026-106380
Vulnerability Analysis
The vulnerability resides in Chrome's UI rendering layer. A crafted HTML page manipulates the visual presentation of browser elements, producing content that mimics trusted interface components. The misrepresentation targets elements users rely on to assess trust, such as address bar indicators, dialog prompts, or permission requests. Successful exploitation requires user interaction, which aligns with the vector component UI:R.
The scope of impact is limited to confidentiality and availability at a low level. The vulnerability does not grant code execution or memory corruption. Instead, it undermines the integrity of trust signals users depend on when evaluating a web page. Attackers typically combine this class of flaw with phishing lures or malicious advertising to maximize impact.
Root Cause
The root cause is improper rendering or layering of UI elements within the browser chrome. Chromium security engineers tracked the issue in Chromium Issue Tracker #553168380. The condition allows web content to overlap, obscure, or mimic authentic browser UI, violating the browser's trust boundary between page content and browser chrome.
Attack Vector
Exploitation requires a victim to visit an attacker-controlled or compromised web page. The attacker crafts HTML, CSS, and potentially JavaScript to render spoofed UI elements that align with the victim's browser version and operating system theme. The victim then interacts with what appears to be a legitimate browser prompt, dialog, or indicator. No authentication is required on the attacker side, and the attack is delivered entirely over the network.
The vulnerability does not expose a public proof-of-concept, is not listed in the CISA Known Exploited Vulnerabilities catalog, and has no reports of in-the-wild exploitation.
Detection Methods for CVE-2026-106380
Indicators of Compromise
- Browser telemetry showing Chrome versions earlier than 155.0.8059.39 connecting to untrusted sites
- User reports of unexpected browser dialogs, permission prompts, or address bar anomalies
- Web proxy logs capturing HTML payloads with heavy overlay styling, fixed-position elements, or UI-mimicking imagery served from newly registered domains
Detection Strategies
- Inventory Chrome installations across managed endpoints and flag any build below 155.0.8059.39
- Monitor DNS and web proxy logs for traffic to domains hosting phishing kits that reference Chrome UI assets
- Correlate credential submission events with recent visits to low-reputation or newly observed domains
Monitoring Recommendations
- Ingest browser version telemetry into the SIEM to track patch compliance over time
- Enable Safe Browsing and enhanced phishing protection reporting on managed Chrome deployments
- Alert on user-reported phishing submissions through corporate reporting channels and prioritize those involving browser UI deception
How to Mitigate CVE-2026-106380
Immediate Actions Required
- Update Google Chrome to version 155.0.8059.39 or later on all desktop endpoints
- Restart browser sessions after update deployment to activate the patched binary
- Validate patch coverage through endpoint management tooling and remediate stragglers
Patch Information
Google released the fix in the Stable Channel update documented in the Google Chrome Desktop Update advisory. Enterprise administrators should use Chrome Browser Enterprise policies or their existing software distribution platform to enforce the minimum version 155.0.8059.39. Chromium-based browsers that inherit the fix should also be updated to the equivalent patched release.
Workarounds
- Enforce Chrome auto-update policies through group policy or configuration management
- Deliver targeted user awareness guidance on recognizing suspicious browser prompts and verifying URLs
- Restrict access to high-risk web categories through secure web gateways until patch deployment completes
# Verify installed Chrome version on Linux endpoints
google-chrome --version
# Windows registry check for enforced minimum version via policy
reg query "HKLM\SOFTWARE\Policies\Google\Chrome" /v TargetVersionPrefix
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

