# CVE-2026-110144: Google Chrome incorrect authorization in Mojo sandbox escape

Source: https://junglewise.ai/threats/cve-2026-110144-incorrect-authorization-in-mojo-in-google-chrome-on-on-windows  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-13. Updated: 2026-10-16  
License: CC BY 4.0 with a link back

CVE-2026-110144 · Severity: high · CVSS 8.6 · Published 2026-10-13

Google Chrome's Mojo inter-process communication component contains an authorization flaw that allows a local attacker to escape the browser sandbox and execute arbitrary code on Windows systems. This could give an attacker code execution privileges comparable to the user running Chrome, potentially leading to full system compromise if the user has elevated privileges.

Technologies: [Google Chrome](https://junglewise.ai/threats/technologies/chrome), [Microsoft Windows](https://junglewise.ai/threats/technologies/windows-). Vendors: [Google](https://junglewise.ai/threats/vendors/google), [Microsoft](https://junglewise.ai/threats/vendors/microsoft).

## Quick answers

**Is CVE-2026-110144 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-110144 being exploited in the wild.

**How severe is CVE-2026-110144?** High severity, with a CVSS score of 8.6, published 13 October 2026.

**Which products and versions are affected?** Google Chrome prior to 155.0.8059.79 on Windows.

**Is there a fix for CVE-2026-110144?** Yes: fixed in Chrome 155.0.8059.79 (Windows and Mac), 155.0.8059.79 (Linux). Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-110144 attacked?** It is attacked with local access, in a web application.

**Am I affected by CVE-2026-110144?** Check whether you run Google Chrome or Microsoft Windows at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in Chrome 155.0.8059.79 (Windows and Mac), 155.0.8059.79 (Linux)

## Technical details

An incorrect authorization vulnerability in Mojo allows a local attacker to bypass sandbox restrictions and achieve arbitrary code execution outside the sandbox. The vulnerability requires local program access on the affected Windows system. The flaw has been fixed in Chrome 155.0.8059.79 and later versions.

## Affected products

- Google Chrome prior to 155.0.8059.79 on Windows

## Timeline

- 2026-10-13: disclosed
- 2026-10-13: advisory

## References

- [https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_01668083673.html](https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_01668083673.html)
- [https://issues.chromium.org/issues/565252396](https://issues.chromium.org/issues/565252396)

## Related threats

- [Google Chrome use after free in Prerender](https://junglewise.ai/threats/cve-2026-110922-use-after-free-in-prerender-in-google-chrome-prior-to-155-0-8059)
- [Google Chrome use-after-free in V8](https://junglewise.ai/threats/cve-2026-110921-use-after-free-in-v8-in-google-chrome-prior-to-155-0-8059-84)
- [Google Chrome memory corruption in V8](https://junglewise.ai/threats/cve-2026-110920-memory-corruption-in-v8-in-google-chrome-prior-to-155-0-8059-84)
- [Google Chrome use after free in V8](https://junglewise.ai/threats/cve-2026-110919-use-after-free-in-v8-in-google-chrome-prior-to-155-0-8059-84)
- [Google Chrome memory corruption in Core](https://junglewise.ai/threats/cve-2026-110918-memory-corruption-in-core-in-google-chrome-prior-to-155-0-8059)