CVE-2026-14109 is a flaw (CVSS 9.6 in the record) in Mojo in Google Chrome before 150.0.7871.47. Insufficient policy enforcement could let an attacker who compromised the renderer escape the sandbox via a crafted page. Chromium rates it Low. Update Chrome 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
- Open chrome://version and check the build is 150.0.7871.47 or later.
- Use About Google Chrome to update and relaunch the browser.
- Confirm your fleet policy lets Chrome update, and relaunch long running sessions.
- Check other Chromium based browsers and embedded runtimes such as Electron apps against their vendor advisories.
- Keep an eye on the Chrome releases blog for new stable updates.
Why it matters
Mojo is the messaging layer Chrome uses between its processes, so a policy check there decides what a sandboxed renderer may ask the privileged side to do. The record lists improper input validation and client side enforcement of server side security. In other words, a rule was checked in the wrong place or not enough.
Chromium rates this Low and the vector yields 9.6, for the same reason as other bugs in the release: the attacker needs a compromised renderer first. The record does not flag the CVE as known exploited.
The record lists these weakness classes: CWE-20 (Improper Input Validation), CWE-602 (Client-Side Enforcement of Server-Side Security).
Quick check
What does client side enforcement mean here?
The record lists CWE-602, which describes a security rule enforced only on the side an attacker may control. The record gives no further detail.
Sources
Last reviewed: 19 October 2026.
