Safeguard
Vulnerability Analysis•

CVE-2026-14104: Input Validation Bug in Chrome WebAppInstalls

CVE-2026-14104 is an input validation flaw in Chrome WebAppInstalls before 150.0.7871.47 that allows code execution inside the sandbox. Update Chrome.

Safeguard Security Team
3 min read

CVE-2026-14104 is a flaw (CVSS 9.8 in the record) in WebAppInstalls in Google Chrome before 150.0.7871.47. Insufficient validation of untrusted input allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted page. Chromium rates it Low. Update to 150.0.7871.47 or later.

What's affected

The record says Google Chrome prior to 150.0.7871.47 is affected. The fixed version is 150.0.7871.47 or later. The record points to the June 2026 Chrome stable channel update post for the desktop release notes. That page loads its content with scripts and did not render for our fetch, so open it in a browser to see the exact build numbers per platform.

Other Chromium based browsers take Chromium fixes on their own schedule, so check each vendor.

How to check if you're exposed

Open chrome://version in the address bar and read the version number. Anything below 150.0.7871.47 is in range. To trigger an update, open the three dot menu, choose Help, then About Google Chrome, and relaunch when asked.

For managed fleets, check the version through your device management console or with a script that reads the installed Chrome version on each platform.

What to do now

  1. Open chrome://version and check the build is 150.0.7871.47 or later.
  2. Use About Google Chrome to update and relaunch the browser.
  3. Confirm your fleet policy lets Chrome update, and relaunch long running sessions.
  4. Check other Chromium based browsers and embedded runtimes such as Electron apps against their vendor advisories.
  5. Keep an eye on the Chrome releases blog for new stable updates.

Why it matters

This one differs from the others in the release. The record says the attacker did not need a compromised renderer first, and that code runs inside a sandbox. The sandbox is the reason Chromium rates the severity Low, while the vector in the record yields 9.8.

It shows why scores and vendor ratings can disagree. The score treats the code execution as the impact, and the vendor weighs the sandbox that limits it. Update either way. The record does not flag the CVE as known exploited.

The record lists this weakness class: CWE-20 (Improper Input Validation).

Quick check

Why is a 9.8 flaw rated Low by Chromium?

The code runs inside the sandbox, which limits what it can reach. The record vector does not capture that, so the numbers differ.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.