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-106285 Overview
CVE-2026-106285 is a user interface misrepresentation vulnerability in the WebAppInstalls component of Google Chrome. The flaw affects Chrome versions prior to 155.0.8059.39 on desktop platforms. A remote attacker can craft an HTML page that misrepresents the web app installation interface, bypassing system access restrictions when combined with social engineering. The weakness is tracked under CWE-451: User Interface (UI) Misrepresentation of Critical Information. Google's Chromium security team rated the internal severity as Low, while the public CVSS v3.1 scoring places the issue in the medium range.
Critical Impact
Attackers can trick users into granting elevated system access to web applications by misrepresenting the Chrome install prompt through a crafted HTML page.
Affected Products
- Google Chrome Desktop versions prior to 155.0.8059.39
- Chromium-based builds sharing the vulnerable WebAppInstalls component
- Installations on Windows, macOS, and Linux stable channels
Discovery Timeline
- 2026-10-06 - CVE-2026-106285 published to the National Vulnerability Database
- 2026-10-07 - Last updated in NVD database
Technical Details for CVE-2026-106285
Vulnerability Analysis
The vulnerability resides in the WebAppInstalls subsystem, which handles Progressive Web App (PWA) installation prompts in Chrome. The component fails to accurately represent the privileges and context associated with an installation request. An attacker-controlled HTML page can manipulate the install surface so that users approve app installation with system-level access they did not intend to grant.
Because the attack vector is network-based and requires user interaction, exploitation depends on luring a target to a malicious page and prompting them to click through the deceptive install dialog. Successful exploitation can bypass system access restrictions tied to installed web applications, including access to privileged capabilities exposed to PWAs.
The EPSS probability currently sits at 0.186%, consistent with a vulnerability that requires meaningful social engineering effort rather than a one-click drive-by chain.
Root Cause
The root cause is improper rendering and context validation in the install flow. The browser presents installation metadata (name, origin, requested capabilities) without sufficient integrity checks to prevent an attacker from spoofing or obscuring the information shown to the user. This maps directly to CWE-451, where critical security-relevant information is misrepresented in the UI.
Attack Vector
Exploitation requires three conditions. First, the victim must visit a crafted HTML page controlled by the attacker. Second, the attacker must convince the user to proceed through the WebAppInstalls prompt. Third, the installed app leverages the bypassed access restrictions to perform actions the user did not authorize. No authentication is required, and the attack is executable remotely over standard HTTPS.
No public proof-of-concept or exploit code is available for CVE-2026-106285. Technical details are tracked in Chromium Issue #533119681.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-106285
Indicators of Compromise
- Unexpected PWA entries under the Chrome chrome://apps listing or the operating system's installed applications list
- Browser process spawning child processes associated with web app shortcuts the user did not knowingly install
- Outbound connections from chrome_proxy.exe or app-mode Chrome instances to previously unseen domains
- User reports of install prompts appearing on unexpected or unrelated websites
Detection Strategies
- Monitor endpoint telemetry for Chrome launched with the --app= or --app-id= command-line flag pointing to unfamiliar origins
- Inspect filesystem writes under the Chrome Web Applications profile directory for new app manifests
- Correlate browser install events with the originating URL to identify suspicious installation sources
Monitoring Recommendations
- Enable browser management policies that log PWA installation events to a centralized SIEM or data lake
- Alert on Chrome versions below 155.0.8059.39 reported by endpoint inventory tooling
- Track user navigation to newly registered domains that subsequently trigger install prompts
How to Mitigate CVE-2026-106285
Immediate Actions Required
- Update Chrome to version 155.0.8059.39 or later across all managed desktops
- Verify auto-update is functional and not blocked by proxy, firewall, or group policy misconfiguration
- Audit installed PWAs across the fleet and remove any that cannot be attributed to a legitimate business need
Patch Information
Google addressed the issue in the Chrome Stable channel release documented in the Google Chrome Stable Update advisory. Chromium-based browsers that rebase on the fixed Chromium milestone inherit the correction. Administrators should confirm vendor-specific release notes for Edge, Brave, Opera, and Vivaldi.
Workarounds
- Disable web app installation via enterprise policy by setting WebAppInstallForceList to an allowlist and configuring DefaultWebAppInstallationBehavior to block unmanaged installs
- Deliver user awareness guidance that no legitimate site should prompt for PWA installation with system access without prior IT coordination
- Restrict Chrome execution in app mode through application control policies where PWAs are not required
# Example Chrome enterprise policy (Windows registry) to restrict PWA installs
reg add "HKLM\Software\Policies\Google\Chrome" /v WebAppInstallForceList /t REG_SZ /d "[]" /f
reg add "HKLM\Software\Policies\Google\Chrome" /v DefaultWebAppInstallationBehavior /t REG_DWORD /d 2 /f
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

