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

CVE-2026-106194: Google Chrome WebAppInstalls RCE Vulnerability

CVE-2026-106194 is a remote code execution flaw in Google Chrome WebAppInstalls affecting versions prior to 155.0.8059.39. Attackers can escape the sandbox through social engineering. This article covers technical details, affected versions, security impact, and mitigation strategies.

Published:

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-106194 Overview

CVE-2026-106194 is a missing authorization vulnerability in the WebAppInstalls component of Google Chrome versions prior to 155.0.8059.39. The flaw allows a remote attacker who has already compromised the renderer process to potentially escape the Chrome sandbox and execute arbitrary code on the host. Exploitation requires social engineering of the user through a crafted HTML page. Google rates the Chromium security severity as Medium, while the NVD assigns a higher CVSS score reflecting the sandbox escape impact. The weakness is tracked as CWE-862: Missing Authorization.

Critical Impact

Successful exploitation chains a compromised renderer with user interaction to execute arbitrary code outside the Chrome sandbox, breaking a core browser security boundary.

Affected Products

  • Google Chrome Desktop versions prior to 155.0.8059.39
  • Chromium-based browsers incorporating the vulnerable WebAppInstalls component
  • All desktop platforms (Windows, macOS, Linux) running the affected Chrome builds

Discovery Timeline

  • 2026-10-06 - CVE-2026-106194 published to the National Vulnerability Database
  • 2026-10-07 - Last updated in NVD database

Technical Details for CVE-2026-106194

Vulnerability Analysis

The vulnerability resides in Chrome's WebAppInstalls subsystem, which handles the installation of Progressive Web Apps (PWAs) and related web application artifacts. The component fails to perform an authorization check before executing a privileged operation requested from the renderer process. Because the renderer is treated as untrusted in Chrome's multi-process architecture, any security-sensitive action triggered by renderer IPC must be validated by the browser process.

An attacker who first compromises the renderer, through a prior memory corruption or logic bug, can then issue install-related IPC messages that reach privileged code paths without proper gating. When combined with user interaction on a crafted HTML page, the attacker can escalate out of the sandbox and run code with the privileges of the browser process.

Root Cause

The root cause is a missing authorization check [CWE-862] in the WebAppInstalls handler. The browser process trusts caller-supplied state from the renderer rather than independently validating that the originating frame, user gesture, and installation context are legitimate. This violates the Chromium rule of least privilege at the IPC boundary.

Attack Vector

The attack vector is network based but complex. The attacker must first achieve renderer compromise, then lure the victim to a crafted HTML page and induce an interaction, such as clicking an install prompt. The crafted page issues install-related messages that the browser process accepts without full authorization, enabling code execution outside the sandbox. No valid exploitation code is publicly available at the time of publication. See the Chromium Issue #498739277 and the Chrome Desktop Update Announcement for vendor details.

Stop Remote Code Execution Before It Runs

Singularity™ Endpoint detects and blocks exploit attempts at machine speed, including zero-days and novel attack techniques.

Stop Exploit Attempts

Detection Methods for CVE-2026-106194

Indicators of Compromise

  • Unexpected PWA or web app installation events on endpoints with no corresponding user administrative action.
  • Chrome child or utility processes spawning non-browser binaries, scripting hosts, or shells shortly after visiting an untrusted site.
  • Writes to Chrome Web App install directories (for example, under the user profile Web Applications folder) from unusual sources.

Detection Strategies

  • Hunt for Chrome browser process children that deviate from the known-good process tree, correlating with recent navigation events.
  • Monitor endpoint telemetry for Chrome versions below 155.0.8059.39 across the fleet and flag outdated installations.
  • Alert on manifest fetches followed immediately by install API calls from frames lacking a legitimate user activation chain.

Monitoring Recommendations

  • Ingest browser process, file, and network telemetry into a centralized data lake for cross-signal correlation.
  • Track Chrome auto-update status and version drift continuously to identify unpatched hosts.
  • Baseline normal PWA install behavior per user population so anomalous installations surface quickly.

How to Mitigate CVE-2026-106194

Immediate Actions Required

  • Update Google Chrome to version 155.0.8059.39 or later on all desktop endpoints.
  • Force a browser restart after update deployment to ensure the patched binaries are loaded.
  • Audit managed Chrome deployments and enterprise policies to confirm automatic updates are enabled and reaching endpoints.

Patch Information

Google addressed CVE-2026-106194 in the Chrome Stable channel update to version 155.0.8059.39. Review the Chrome Desktop Update Announcement for the full list of fixes and the Chromium Issue #498739277 for upstream tracking. Chromium-based browsers that embed the affected code should ship equivalent patches on their own release cadence.

Workarounds

  • Disable web app installation through enterprise policy by setting WebAppInstallForceList to an empty list and restricting DefaultWebAppManagement where supported.
  • Restrict user navigation to untrusted sites with URL allowlists or secure web gateway controls until patching completes.
  • Educate users to decline unexpected install prompts, as exploitation requires user interaction on a crafted page.
bash
# Verify installed Chrome version meets the fixed build
google-chrome --version
# Expected output: Google Chrome 155.0.8059.39 or later

# Linux example: enforce update channel via policy
sudo tee /etc/opt/chrome/policies/managed/chrome_update.json >/dev/null <<'EOF'
{
  "DefaultBrowserSettingEnabled": true,
  "ComponentUpdatesEnabled": true,
  "WebAppInstallForceList": []
}
EOF

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

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.