Cybersecurity & Privacy

Chrome 156 Fixes 52 Flaws as Claude Shows a Full Browser Escape

Chrome 156 fixes four critical flaws and credits AI-assisted researchers. Anthropic also showed a Mac sandbox escape and detailed attacks on other systems.

By Marcus Lee Edited by Samantha Reed Published: Updated:
Chrome 156 Fixes 52 Flaws as Claude Shows a Full Browser Escape
Chrome 156 patches serious security flaws as AI-assisted research demonstrates browser sandbox escapes. Photo: Daniil Komov / Pexels

Key Notes

  • Google’s Chrome 156 desktop update includes 52 security fixes, with four rated critical and credits for AI-assisted vulnerability research.
  • Anthropic demonstrated a macOS browser sandbox escape using an unreleased internal model and says its broader Chrome findings were patched by version 156.
  • Users should install the latest available browser update and relaunch, while separate Safari and operating-system issues require their own platform updates.

Google has released Chrome 156 with 52 security fixes, including four rated critical, as AI-assisted research exposes increasingly serious browser weaknesses. The October 27 release notes credit Claude-assisted researchers and OpenAI Codex Security among the contributors.

Separately, Anthropic demonstrated a Chrome attack chain that launched the macOS Calculator app after a malicious page loaded, escaping the browser’s sandbox without further interaction. Its work used an unreleased internal research model, so the demonstration should not be read as a capability available to every ordinary Claude user.

A Web Page That Escaped Chrome’s Sandbox

In its research report, Anthropic describes a proof of concept that executed code outside Chrome’s protections on a default-configuration Mac. Calculator served as visible evidence that the chain had reached beyond the web page.

A browser sandbox is meant to contain a compromised page or rendering process. Crossing that boundary is more consequential than making a tab crash: it can allow code to run with the logged-in user’s privileges. The demonstration illustrates why security teams examine combinations of bugs, rather than treating every flaw as an isolated problem.

Anthropic says 62 Chrome CVEs from its research had been patched by Chrome 156, including 13 sandbox escapes. That is a different figure from the 52 fixes listed in Google’s specific desktop release. The two totals should not be combined or treated as interchangeable counts for this update.

Our earlier coverage of an XBOW Chrome exploit showed another example of AI-assisted vulnerability research. The broader development is that models are helping researchers connect weaknesses into working demonstrations, making the speed of testing and patch deployment increasingly important.

The Findings Reach Beyond Chrome

The same Anthropic report describes four other attack chains. In Apple’s Safari, a chain bypassed website isolation and accessed sensitive browsing data. A separate Android demonstration extracted information from a locked Pixel 9 through a physical USB connection.

On Linux, the company reported remote root-level command execution against servers with a vulnerable multipath TCP listener. The Windows example concerned remotely crashing machines that exposed the affected native HTTP/3 implementation, rather than taking control of every Windows computer.

Anthropic says the affected vendors addressed these issues. A Chrome update does not install those separate operating-system or Safari fixes; each platform has its own update process. The findings also differ in prerequisites, so a physical-access phone attack should not be presented as equivalent to visiting a malicious web page.

Install the Update, Then Relaunch

Google lists desktop builds 156.0.8078.73/.74 for Windows and Mac, and 156.0.8078.73 for Linux, with rollout taking place over the coming days and weeks. Chrome users should check for the latest available update rather than assume an open browser has already applied it.

On Windows or Mac, Google’s update guide directs users to the three-dot menu, Help and About Google Chrome, then Relaunch when an update is ready. Linux users should update through their package manager. Installing an available update and restarting the browser are the practical steps that turn a published fix into protection on a device.

For developers, the story is also about prevention. Finding an old vulnerability helps repair existing software; checking new changes can reduce the next backlog. That is the same defensive direction behind tools such as Anthropic’s OSS Scanner, although a scanning service is no substitute for shipping and applying a fix.

Disclaimer: AIstify is an independent media brand owned and operated by NuvexMedia LLC, publishing news, research, and insights on artificial intelligence, emerging technologies, automation, and related industries. NuvexMedia LLC invests in and collaborates with companies across the AI, technology, software, and digital innovation sectors. These relationships do not influence AIstify’s editorial coverage, and the publication maintains full editorial independence to provide accurate, timely, and objective information. © 2026 NuvexMedia LLC. All rights reserved. This content is for informational purposes only and should not be considered legal, tax, investment, financial, or other professional advice.

AI & Machine Learning, Cybersecurity & Privacy, News