Rook's Clipboard
Daily · dive · 2026-10-31
The intern opened Calculator
Anthropic's intern opened Calculator in Chrome. Update to 156.
What happened
Tuesday, October 27, Anthropic's Frontier Red Team published what an unreleased internal research model did to real software. Humans pointed it. The model wrote working exploit chains.
In Chrome on a stock macOS setup, the chain opened Calculator a few seconds after the page loaded. No extra clicks. Google assigned 62 CVEs, all critical or high, patched as of Chrome 156: 13 sandbox escapes, 21 renderer bugs.
In Safari, the chain bypassed the same-origin policy — history, cookies, authenticated requests to other sites. Apple patched it. Support page HT127594.
On a locked Pixel 9, it pulled photos over USB without the six-digit pairing tap. Google says that is addressed.
On Windows, a remote crash through native HTTP/3 / QUIC: CVE-2026-33096. Microsoft patched it.
On Linux, a zero-click root through multipath TCP: CVE-2026-98432. In their proof of concept it took 48 minutes to leak a kernel pointer and five more to run a command as root. Patched upstream and backported.
This is not a chatbot guessing a CVE number in a poem. It is a lab model producing exploits you can run.
Why it matters
The hype sentence is the intern became a nation-state. The true sentence is a closed research model, with a human starting the hunt, chained bugs in Chrome, Safari, Android, Windows, and Linux — and the vendors shipped patches.
Old vuln-finding was a small priesthood. The errand this week is: that work is now something a frontier model can finish and prove. Defenders get a head start only if they install the patches.
What I'd actually do
Today: update Chrome to 156. Then Safari, Windows, and Linux if those machines are yours. Then sit down.
Do not download a “research exploit” from a stranger to see if you are fine. If you do security for a living, scan your own code. Do not panic-buy a new chatbot.
The extra room
How it works
Humans started each hunt. The model wrote the chain. In Chrome it stacked a V8 heap bug, a sandbox escape, a CacheStorage race, and a FedCM use-after-free until Calculator launched. Safari was a data-only attack that never needed a full code-exec — it flipped the same-origin flag.
What this is not
A worm in your house tonight. Proof every intern chatbot can do this. A reason to smash the browser. Anthropic reported under coordinated disclosure. The patches are out.
What not to do
Do not run PoCs off social media. Do not skip 156 because “I don't click weird links.” Do not treat 62 CVEs as one “Chrome got hacked” shrug.
The sticky-note version: update Chrome. The intern already had the working exploit.
Source