The research

Anthropic's Frontier Red Team published a research post on 27 October describing how, over the past few months, it has used an unreleased internal research model to find critical vulnerabilities in some of the world's most widely used software — browsers and operating systems — and chain them into working exploits. The post shares details of five attack chains that led to remote code execution and other critical impacts with little to no user interaction.

The team describes these products as a bellwether for model vulnerability-research and cyber capabilities: any vulnerability in them could affect billions of users, and they are among the most security-critical software in the world. Each finding was reported under coordinated vulnerability disclosure — 90 days for developers to patch, 45 additional days before details beyond a public advisory are discussed.

The Chrome chain

After initial prompting, the model wrote a full exploit chain enabling arbitrary code execution outside Chrome's sandbox. The proof of concept launches the Calculator app from a stock default-configuration Chrome browser on macOS within seconds of page load, without further user interaction.

The chain used four flaws: a V8 heap corruption from a malicious page, a second bug escaping V8's memory sandbox and defeating ASLR via a return-oriented programming chain, a race condition in CacheStorage to read memory outside the sandbox, and a use-after-free in FedCM, Chrome's federated sign-in feature, to execute arbitrary code outside the sandbox. Anthropic says 62 CVEs were assigned and patched as of Chrome 156, all critical or high, including 13 sandbox escapes.

The Safari chain

The Safari exploit is notable because it is a data-only attack: the model chained a JavaScriptCore use-after-free with weaknesses across WebKit's Gigacage and the WebContent sandbox to obtain full read/write access to the browser process memory, then changed a single value to disable the same-origin policy. With that rule off, a malicious page can read a user's history and cookies and send authenticated requests to other domains — reading email or viewing bank balances if the user is signed in.

Apple acknowledged the report the same day and implemented a fix, available to users as of the 26.5.2 releases. Apple credits 'Milad Nasr and Nicholas Carlini with Claude, Anthropic' for the fix; Google's release notes similarly credit Anthropic engineers assisted by Claude for specific Chrome fixes.

Other platforms

The other chains show the model generalizes across platforms: an Android lock-screen bypass that extracts photos from a stolen Pixel 9 via three chained vulnerabilities; a Windows remote denial of service against the native HTTP/3 QUIC implementation, assigned CVE-2026-33096, where a few packets over the network can crash and continuously restart a server; and a Linux root RCE over the network against a multipath TCP listener, patched as CVE-2026-98432 on October 15.

Anthropic also reports local privilege escalation vulnerabilities on OpenBSD, FreeBSD and Linux, sandbox escapes in popular infrastructure, and numerous web application vulnerabilities found with strategies ranging from pure coverage to goal-based and threat-model-based testing — all passing through a standardized verification and risk-rating pipeline.

How to read it

Independent observers note the verifiable parts are the patches: Google and Apple publicly credit Anthropic engineers with specific fixes, and the CVEs are public. What cannot be independently checked is how much of each chain the model built on its own — Anthropic does not break down human involvement at each step, does not name the model, and provides no success rates, costs or human-hours per chain, as Black Duck's Andrew Bolster noted.

The safety-relevant bottom line is unchanged by those caveats: a frontier lab's model has demonstrated the ability to assemble zero-click and one-click chains against stock browsers and operating systems. The fact that all findings were disclosed and patched is the responsible-outcome part of the story; that such chains are now model-assemblable is the risk part.

What the chains mean for safety

For safety researchers, the meaningful coordinate shifted: model capability is no longer the binding constraint on whether advanced exploit chains get built, because a lab model has now demonstrated it can assemble them across the most security-critical software in the world. The real questions are whether models will do this on behalf of defenders far more than attackers, and whether disclosure norms keep pace with capability.

Anthropic framed the work as a bellwether for model vulnerability research and cyber capabilities, published under its Frontier Red Team. The same research program that finds these bugs also informs the company's safety decisions about when and how to release model capabilities. The fact that every finding was reported to the vendor and is now patched is the standard that makes publishing this kind of research defensible.

Caveats

Anthropic did not release the model, did not disclose its name or training details, and its account does not break down how much human assistance was involved at each step. Independent observers can verify the vendor patches and the credit lines in Google and Apple release notes, but they cannot verify the model's level of autonomy.

The 90-day disclosure window means some details in the post are already public via advisories; others will become clearer as vendor patch notes accumulate. None of the described exploits are known to have been used in real-world attacks.

Common questions

Did Claude find real vulnerabilities?

Yes — 62 CVEs in Chrome plus chains in Safari, Android, Windows and Linux; all reported to vendors and patched.

Was the model used in real attacks?

No — the exploits were built in the lab after prompting and never used against real users.

Which model was it?

An unreleased internal research model, which Anthropic has not named.

Sources & further reading

  1. Discovering and exploiting vulnerabilities in critical, real-world software with Claude ↗
How this story was made

Written by Kristian Kostov with AI assistance and checked against the linked sources. Company performance claims are attributed to the company. Analysis reflects AiLookout’s interpretation; we have not independently tested the products discussed. The cover is an AI-generated editorial illustration, not a photograph or evidence of an actual event.

Our editorial standards
Back to all stories