Claude Opus wrote a Chrome exploit for $2,283
Mohansrk
18 points
11 comments
April 18, 2026
Related Discussions
Found 5 related stories in 97.4ms across 9,294 title embeddings via pgvector HNSW
- Google published exploit code for an unfixed Chromium bug logickkk1 · 28 pts · May 20, 2026 · 64% similar
- Chromium publishes fixed exploit 4 years later, turns out it's unfixed birdculture · 20 pts · May 21, 2026 · 58% similar
- Claude Code Found a Linux Vulnerability Hidden for 23 Years eichin · 25 pts · April 03, 2026 · 55% similar
- A 0-click exploit chain for the Pixel 10 happyhardcore · 353 pts · May 15, 2026 · 52% similar
- "Dirty Frag" (CVE-2026-43284): The Second Linux Root Exploit in Eight Days ggallas · 31 pts · May 09, 2026 · 51% similar
Discussion Highlights (4 comments)
pingou
I know most people here hate that, but I think this makes a much stronger case for security by obscurity (not releasing the source code) in these changing times. Of course security by obscurity by itself is by no mean sufficient.
localhoster
> "A week of back and forth, 2.3 billion tokens, $2,283 in API costs, and about ~20 hours of me unsticking it from dead ends. It popped calc." Corrent me if I'm wrong, I'm not a security researcher, but 20 hours, a week of work, 2283$ spent and over 2 trillion tokens, is not very 10x-ing as we were promised. Especially if you take into account that the guy is at least half capable for this take. I dunno
ofjcihen
This has been what I’ve been screaming from the rooftops for a while, that these models can already do this. Go read the devs actual blog though. This is more a statement on patch lag than anything else. In my mind that’s much more important than “zomg zero days!!!”
jdndnejdn
A security researcher instructed an LLM to write an exploit for a know bug fixed in an already published release Not really impressive