Loading vulnerability…
Remote Code Execution in Google Chrome Network Component
CVE-2026-110161 is a critical use-after-free vulnerability in the Network component of Google Chrome before version 155.0.8059.79. A remote attacker can trigger the vulnerability through crafted network traffic to execute arbitrary code outside the browser sandbox. The specific vulnerable function and object lifetime conditions have not been disclosed. The vulnerability has a reported CVSS v3 base score of 9.6.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation permits arbitrary code execution outside Chrome's sandbox, potentially compromising the affected system and exposing data and resources accessible to the exploited process. Confidentiality, integrity, and availability impacts are rated high. Execution outside the sandbox does not by itself establish administrative or system-level privileges.
If you can’t patch tonight, do this now.
No vulnerability-specific temporary workaround is documented. Running Chrome under a non-administrative account and restricting access to untrusted destinations through URL and DNS filtering can reduce potential impact and exposure, but do not correct the vulnerability or replace patching. Chrome's built-in sandbox alone is insufficient because successful exploitation permits execution outside it.
Patch, then assume compromise.
Upgrade Google Chrome to version 155.0.8059.79 or a later applicable fixed release and relaunch the browser. The desktop security release provides versions 155.0.8059.79/.80 for Windows and Mac and 155.0.8059.79 for Linux. Update distribution-managed Chromium through the package manager; Debian stable (trixie) provides the fix in version 155.0.8059.79-1~deb13u1 or later. Confirm that the installed distribution package includes the fix rather than relying on inconsistent advisory text naming version 155.0.8059.39.
No public exploits tracked yet. Mallory keeps watching.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
21 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.