🔍 Read the full analysis: Anthropic’s AI Built Five Attack Chains: Separating Evidence From Implications on ThorstenMeyerAI.com
Prime made for students and young adults
- Fast, free delivery for dorm and study essentials
- Prime Video and Amazon Music included
- Member-only deals
TL;DR
Anthropic’s Frontier Red Team said on October 27 that an unreleased research model identified flaws and built five working exploit chains across Chrome, Safari, Android, Windows and Linux in laboratory testing. Vendor records credit Anthropic researchers and Claude for some fixes, but the model’s identity, human contribution and public documentation for the Android chain remain unclear.
Anthropic’s Frontier Red Team said October 27 that an unreleased research model called Claude identified software flaws and combined them into five working exploit chains affecting Chrome, Safari, Android, Windows and Linux. Anthropic says it reported the flaws to the relevant vendors before publication; the report describes laboratory demonstrations, not attacks observed in the wild.
Anthropic said the model produced the chains “after initial prompting” and with “little human involvement,” but did not identify the model or provide a detailed account of what researchers did. The company described the work as a shift from finding individual bugs to connecting weaknesses across security layers to produce a functioning attack. That claim is based on Anthropic’s account of its research, and the article does not establish that the model acted independently.
The reported demonstrations varied in access and impact. Anthropic’s Chrome example used a page visit to run code on a Mac as the logged-in user, outside Chrome’s sandbox; the proof of concept opened Calculator without another user action. The Safari chain, as described by Anthropic, could disable a browser protection and let a malicious site read or alter data from other sites. The report also describes an Android chain requiring physical access to a locked phone, a Windows chain, and a Linux chain that could allow remote command execution as root on certain servers.
Some parts can be checked against vendor records. Anthropic says its Chrome reports led to 62 CVEs patched by Chrome 156, a cumulative figure that the source could not reconcile with Google’s release notes. Google’s October 20 Chrome 156 notes list 353 security fixes and credit Anthropic researchers on several entries, including five that explicitly say they were assisted by Claude. Apple’s advisory for iOS and iPadOS 26.5.2 credits Anthropic researchers “with Claude” for a WebKit flaw. Microsoft’s advisory for CVE-2026-33096 also credits Anthropic researchers working with Claude. The source reports finding no public record for the Android chain.
Infographic 01 · What the model built
Five chains, five very different threats.
Anthropic says an unreleased Claude research model found the flaws and chained them into working exploits. All were reported to the vendors first; none is listed as exploited.
What it doesRuns code on the Mac, outside the browser sandbox
What it needsOne page visit, stock Chrome on macOS
FixedChrome 156, 20 Oct
vendor recordWhat it doesAny website reads data from your other sites
What it needsOne page visit
FixediOS / iPadOS 26.5.2, 29 Jun
vendor recordWhat it doesCopies photos off a locked, stolen phone
What it needsThe phone in hand, over USB
Fixed“Addressed by Google”
Anthropic's wordWhat it doesCrashes a server; repeat to keep it down
What it needsServer answers HTTP/3 (built-in)
FixedCVE-2026-33096, 14 Apr
vendor recordWhat it doesRuns commands as root, no login, no click
What it needsServer with a multipath TCP listener
FixedCVE-2026-98432, 15 Oct
CVE yes, link: AnthropicConfirmed in vendor records
- Chrome 156: 353 security fixes, 15 credited to an Anthropic researcher (4 critical, 11 high; my count)
- Apple: CVE-2026-43715 credited to two Anthropic researchers “with Claude”
- Microsoft: acknowledges an Anthropic researcher and Calif.io “with Claude”
- Linux: CVE published, rated 9.8, fixed in stable kernels
Anthropic’s word only
- That the model did the chaining “after initial prompting”
- “Little human involvement”, with no breakdown
- 62 Chrome CVEs in total, and the Android fix
- Which model it was: “unreleased, internal research model”
Five platforms are not five equal threats: two need only a page visit, one a stolen phone, one only crashes servers, one takes them over.Thorsten Meyer · my reading
Sources: Anthropic Frontier Red Team, 27 Oct 2026; Chrome 156 notes, 20 Oct; Apple iOS 26.5.2, 29 Jun; Microsoft CVE-2026-33096, 14 Apr; CVE-2026-98432, 15 Oct; CISA KEV, 28 Oct 2026. Counts in the Chrome notes: Thorsten Meyer.
Powered by Thorsten Meyer AI
Shorter Paths From Bug to Exploit
The reported work matters because a software flaw is not always enough to compromise a device. Browsers and operating systems use layers of protection, so an attacker may need to connect several weaknesses to cross a sandbox, gain access to a more privileged process or reach sensitive data. If AI systems can reliably help assemble those steps, defenders may have less time between a flaw becoming known and a practical exploit being developed.
That is a potential risk, not evidence that these demonstrations were used against people. Anthropic says the work took place in a lab and that it disclosed the flaws to vendors. The source also cites a separate Anthropic lab test published in June in which a model turned a public Firefox fix into a working exploit in under an hour. That is the company’s measurement in a controlled test, not a measure of real-world attacks or proof that every model can do the same.
The defensive implications cut both ways. Security teams may use AI to find and validate flaws faster, while attackers could seek similar assistance. Anthropic says its public models block most cyber work and that vetted security teams can apply for broader access; the source notes that OpenAI has a similar program. Those safeguards do not establish how well other systems are controlled, or how quickly the capabilities may spread.
Popular right now

Vitamix Propel Series 510 Professional-Grade Blender, 3 Programs, Black

Bose QuietComfort True Wireless Earbuds with Active Noise Cancellation, Black

Shark HydroVac MessMaster Corded Wet/Dry Vacuum, Mop & Self-Clean (WD161)
As an affiliate, we earn on qualifying purchases.
Five Chains, Different Access Needs
An exploit chain combines multiple weaknesses or behaviors so that an attacker can reach an outcome a single flaw may not allow. Anthropic’s examples are not interchangeable: the Chrome demonstration began with a web page, while its Android scenario required a stolen phone in hand. The Linux chain was described as remote root command execution on certain servers. Those differences affect who could be exposed and what protections may help.
Anthropic says its researchers reported each flaw to the affected vendor before the findings were published. The source identifies patched records for Chrome, Apple’s WebKit and Microsoft’s CVE-2026-33096. It gives a public severity score of 9.8 out of 10 for the Linux flaw, but does not provide the CVE identifier in the supplied material. The Chrome 156 release notes list hundreds of security fixes, so the vendor’s acknowledgement of researchers does not by itself verify Anthropic’s full cumulative count of 62.
The source compares the risk of faster exploit development with the 2017 WannaCry attack, which it says began 59 days after Microsoft released a patch. That is a historical comparison, not a prediction that the same timeline will apply here. Anthropic’s June Firefox test is also separate from the five chains announced in October and should be understood as a company-reported laboratory result.
What the Records Do Not Show
The public material leaves important details unresolved. Anthropic has not named the research model, supplied a task-by-task account of human involvement or published enough information in the supplied source to independently reproduce all five chains. The Android chain is especially difficult to verify from the source: its author says no public record was found. The supplied account also cuts off during its Android description, so the reported access conditions and technical details cannot be fully assessed here.
It is also unclear how Anthropic arrived at its total of 62 Chrome CVEs and how that number maps to Google’s Chrome 156 release notes. Vendor acknowledgements confirm credit for some reported work, but they do not confirm every claim about the model’s role, the full exploit chains or their performance outside a lab. The source says fixes are available, yet does not provide a complete list of affected versions or establish whether every relevant device and server has been updated.
Anthropic says the demonstrations were controlled and disclosed responsibly. The source provides no evidence that the five chains were used in real attacks, and no independent testing is described that would show how reliably the model could repeat the results without expert guidance.
Patch Status and Independent Checks
For users and administrators, the immediate step is to install current browser, operating-system and server updates, then restart devices when an update requires it. Anthropic’s report says the flaws were reported to vendors and that fixes are out, but readers should check the advisories for their specific products rather than assume every device received an update automatically.
The next useful evidence would be clearer public records linking each demonstration to a vulnerability identifier, affected versions, vendor fixes and any remaining exposure. A fuller account of the model’s identity and the division of work between Claude and human researchers would also help researchers evaluate how much of the result was automated. Until then, the findings are a warning about a possible acceleration in exploit development, not confirmation of an active, widespread threat.
Key Questions
Did Anthropic say these attacks happened in the wild?
No. Anthropic described laboratory demonstrations and said it reported the flaws to vendors. The supplied source provides no evidence that the five chains were used in real attacks.
Which products were included in the five reported chains?
Anthropic named Chrome, Safari, Android, Windows and Linux. The reported access and outcomes differed across platforms, and the supplied source does not provide complete technical details for every chain.
Can the claims be independently checked?
Some elements can be checked in vendor records. Google, Apple and Microsoft advisories include credits to Anthropic researchers, with some references to Claude. The source says it could not reconcile Anthropic’s total of 62 Chrome CVEs with Google’s release notes and found no public record for the Android chain.
What should users do now?
Install available browser and operating-system updates, and restart devices when required. Administrators should check vendor advisories for the products and versions they manage; the report does not establish that all systems are patched automatically.
What remains unknown about Claude’s role?
Anthropic has not named the research model or given a detailed breakdown of human involvement. Vendor credits support some collaboration with Claude but do not independently verify the model’s contribution to every reported chain.
Source: ThorstenMeyerAI.com
