Pinned Tweet
@QED_Audit found CVE-2026-19174, an integer overflow in V8 that gives you arbitrary code execution in Chrome. The bug is one line of constant arithmetic. It survived 3.5 years of fuzzing, manual audit, and LLM-driven review. (1/n)
3
15
111
27,165
We didn't make it into this year's Pwn2Own, but we still pwned five targets.
Hopefully we'll be able to publish the vulnerabilities soon, along with walkthroughs of how we broke each one.
Had a lot of fun collaborating with @qvipinb at @vert3x_io 🫡
3
8
84
8,454
Also from @vert3x_io, go follow them!
Thank you for collaborating w/ us! We’re all pretty let down that we didn’t get in :(
@QED_Audit x @vert3x_io will be responsibly disclosing all vulnerabilities found, and all PoCs will be dropped soon™. Be on the lookout for some other cool hardware disclosures 👀
ALT Music Assistant -> HAOS Root chain
ALT Phillips Hue Bridge Pro RCE + SBX
1
1
5
853
*6 targets
We didn't make it into this year's Pwn2Own, but we still pwned five targets.
Hopefully we'll be able to publish the vulnerabilities soon, along with walkthroughs of how we broke each one.
Had a lot of fun collaborating with @qvipinb at @vert3x_io 🫡
4
604
1/
We found a full collision for the Poseidon1 Collision Prize instance and submitted it on July 31.
Two different messages, identical 16-word output after all 28 rounds, verified on the Initiative's official implementation.
The technical breakdown and full story ⬇️
1
12
93
9,657
6/
LLMs are accelerating cryptography on both sides. Claude found a new HAWK attack, McEliece is under pressure after 50 years, and Poseidon saw a wave of new cryptanalysis in weeks.
On the other side, AI autoresearch made SHA/BLAKE cheap to prove(snark.fast). Ethereum L1 is moving from Poseidon to SHA/BLAKE.
1
2
551
7/
With LLMs in the loop, cryptosystems will be contested harder than ever. Only the safe, efficient ones survive.
Matrix M, both messages, verifier: github.com/ainta/poseidon1-c…
ePrint: eprint.iacr.org/2026/1760
Blog: qedaudit.io/blog/poseidon-co…
1
5
1,396
During my time at @QED_Audit I circled back and took another quick look at browser/JSE vulnerability research. AI agents flying high, seemingly finding & exploiting bugs everywhere, and there's this: a **constant integer overflow** in V8, alive for over 3.5 years. (1/5)
@QED_Audit found CVE-2026-19174, an integer overflow in V8 that gives you arbitrary code execution in Chrome. The bug is one line of constant arithmetic. It survived 3.5 years of fuzzing, manual audit, and LLM-driven review. (1/n)
2
25
147
17,310
@QED_Audit found CVE-2026-19174, an integer overflow in V8 that gives you arbitrary code execution in Chrome. The bug is one line of constant arithmetic. It survived 3.5 years of fuzzing, manual audit, and LLM-driven review. (1/n)
3
15
111
27,165
This one was found and exploited end-to-end with Claude Opus 5 under moderate human supervision of @0x10n, a seasoned Chrome security researcher and the author of ExploitBench. (14/n)
1
692
Full writeup, including the exploit and the upstream fix:
qedaudit.io/blog/brilliantly… (15/n)
6
20
1,853