Quick answers
- Is CVE-2026-110161 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-110161 being exploited in the wild.
- How severe is CVE-2026-110161?
- 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-110161?
- Yes: fixed in Chrome 155.0.8059.79 and later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-110161 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-110161?
- 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 and later
Technical details
A use-after-free flaw in Chrome's Network component allows arbitrary code execution outside the sandbox when processing malicious network traffic. The vulnerability requires network access and no user interaction beyond visiting a webpage or receiving network traffic. Successful exploitation grants an attacker code execution with the privileges of the browser process, escaping sandbox protections.
Affected products
- Google Chrome prior to 155.0.8059.79
Timeline
- 2026-10-13: disclosed: Fixed in stable release 155.0.8059.79
- 2026-10-02: other: Reported by Google