# CVE-2026-110159: Google Chrome incorrect authorization in Updater

Source: https://junglewise.ai/threats/cve-2026-110159-incorrect-authorization-in-updater-in-google-chrome-prior-to-155  
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-110159 · Severity: critical · CVSS 9.6 · Published 2026-10-13

Google Chrome's Updater component contains an authorization flaw that allows a local attacker to execute arbitrary code outside the browser sandbox. A user with local access to a machine running vulnerable Chrome can exploit this to gain code execution with elevated privileges, potentially compromising the entire system and data stored on it.

Technologies: [Google Chrome](https://junglewise.ai/threats/technologies/chrome). Vendors: [Google](https://junglewise.ai/threats/vendors/google).

## Quick answers

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

**How severe is CVE-2026-110159?** Critical severity, with a CVSS score of 9.6, published 13 October 2026.

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

**Is there a fix for CVE-2026-110159?** Yes: fixed in Chrome 155.0.8059.79 (Windows/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-110159 attacked?** It is attacked with local access, in a web application.

**Am I affected by CVE-2026-110159?** Check whether you run Google Chrome 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/Mac), 155.0.8059.79 (Linux)

## Technical details

An incorrect authorization check in the Updater component allows a local attacker to execute arbitrary code outside the sandbox. The vulnerability requires local program execution but does not require authentication or elevated privileges, making it exploitable by any local user on the system.

## Affected products

- Google Chrome prior to 155.0.8059.79

## Timeline

- 2026-10-13: disclosed
- 2026-10-13: patched

## 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/564573066](https://issues.chromium.org/issues/564573066)

## Related threats

- [Google Chrome out of bounds read in Skia](https://junglewise.ai/threats/cve-2026-126922-out-of-bounds-read-in-skia-in-google-chrome-prior-to-157-0-8103)
- [Google Chrome use after free in Accessibility](https://junglewise.ai/threats/cve-2026-126921-use-after-free-in-accessibility-in-google-chrome-prior-to-157-0)
- [Google Chrome information leak in Skia](https://junglewise.ai/threats/cve-2026-126920-information-leak-in-skia-in-google-chrome-prior-to-157-0-8103-78)
- [Google Chrome use-after-free in BrowserTag](https://junglewise.ai/threats/cve-2026-126919-use-after-free-in-browsertag-in-google-chrome-prior-to-157-0)
- [Google Chrome use-after-free in Layout](https://junglewise.ai/threats/cve-2026-126918-use-after-free-in-layout-in-google-chrome-prior-to-157-0-8103-78)