ExploitGym – Can AI Agents Turn Security Vulnerabilities into Real Attacks?
GPT-5.4 was given a five-line PoV that triggers an assertion in Maglev, V8's mid-tier JIT compiler, reported by ClusterFuzz after GPT-5.4's knowledge cutoff. On the release build, the PoV just throws a benign TypeError with no visible memory corruption. Total time: 71 minutes, 229 lines of exploit code.
- ▪GPT-5.4 was given a five-line PoV that triggers an assertion in Maglev, V8's mid-tier JIT compiler, reported by ClusterFuzz after GPT-5.4's knowledge cutoff.
- ▪On the release build, the PoV just throws a benign TypeError with no visible memory corruption.
- ▪Total time: 71 minutes, 229 lines of exploit code.
Hacker News (AI / LLM) files mainly under ai. We currently carry 3,301 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Cybergym |
| Canonical URL | https://www.cybergym.io/exploitgym/ |
| Publication time | Sat, 25 Jul 2026 21:17:09 +0000 |
| Retrieval time | 2026-07-25T21:27:28.934Z |
| Last seen | 2026-07-25T21:27:28.934Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | 1h60dJ-2_kEI |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
GPT-5.4 was given a five-line PoV that triggers an assertion in Maglev, V8's mid-tier JIT compiler, reported by ClusterFuzz after GPT-5.4's knowledge cutoff. On the release build, the PoV just throws a benign TypeError with no visible memory corruption. From there the agent independently escalated through a full exploit chain: it identified that the bug depends on receiver shape, tricked Maglev into an out-of-bounds heap read, groomed the heap to leak stable pointers, forged fake V8 string objects to obtain arbitrary native memory reads, leaked libc addresses from the Global Offset Table, and built a signal-return-oriented-programming chain redirecting execution to system("/challenge/catflag"). Total time: 71 minutes, 229 lines of exploit code.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Cybergym.
Discussion
0 commentsMore from Cybergym
