On 28 October Google announced Gemini 4 Carbon, the successor to Gemini 4 Argon, in a post by Koray Kavukcuoglu. Carbon goes first to “a subset of cyber defenders” through the Fairwind Program, with wider release promised but not dated. The post leads on security. “Carbon achieves a state-of-the-art 88.2% on SEC-bench Pro,” it says, and it “sets a new state-of-the-art on the popular exploitation benchmark ExploitGym (54.8%).” For patching, “Carbon reaches 71.0% on Collinear’s CWE-bench.”
When Argon launched I wrote that its results table had one cyber row. Carbon’s post has three cyber numbers, which is more. So I went to check each one where the benchmark keeps its own results.
Three numbers, three kinds of evidence
SEC-bench Pro is a long-horizon security benchmark from a paper posted to arXiv in May. Its public leaderboard has an overall board of 344 tasks across V8, Firefox and Linux. The top entry there is GPT-5.5 at 58.4%, solving 201 of the 344. No Gemini model appears on any of its boards, so Carbon’s 88.2% is Google’s own run, reported in a blog post.
ExploitGym also comes from a May arXiv paper, and its repository describes 869 task instances. The repository page has no leaderboard and no scores, so the 54.8% has nothing public to sit beside.
CWE-bench is different. It is run by Collinear on a private set of 120 tasks, and its v1 leaderboard lists Gemini 4 Carbon first, at 71% programmatic pass@1. That is the one claim in the post that a reader can check against a table the benchmark’s owner publishes.
The checkable one is a three-point lead
On CWE-bench v1 the ordering is tight. Carbon has 71%. Three models tie at 68%: Grok 4.7, GPT-6 Astra and Google’s own Gemini 4 Argon. Claude Opus 5.5 has 67%. The Argon report, which describes the benchmark in detail, says each model runs four independent trials per task and that Pass@1 is the mean success rate across all 120 tasks.
On 120 tasks, one task is worth about 0.83 points, so Carbon’s lead over the next three models is about three and a half tasks on average. Four trials per task steady the run-to-run noise. They do nothing about the fact that 120 tasks is a small sample of what security audits look like; by my arithmetic the binomial standard error of a 70% score on 120 tasks is a little over 4 points, larger than the lead. The benchmark’s own judge panel, scored separately, puts Carbon at 71% and GPT-6 Astra at 66%, which is a wider gap, and the ordering below the top changes between the two columns.
The other two have no table to sit beside
The SEC-bench Pro comparison is the hardest to read. Carbon’s 88.2% is 30 points above the best entry on the public board, which is GPT-5.5 at 58.4%. That gap is not a like-for-like comparison. The public board’s newest entries are older models, and none of the October 2026 frontier models is on it, so the 58.4% says more about who has submitted than about where the field is. The comparison a reader would want, Carbon next to GPT-6 Astra and Claude Opus 5.5 on the same 344 tasks with the same harness and budget, is not published anywhere I could find.
ExploitGym has the same gap with less around it. The repository describes the task set and points to a submission format, but no scores are posted, so “a new state-of-the-art” is a claim about runs that only Google has published a number for.
The post does link a “Safety and Security report.” The link goes to the Gemini 4 Argon Safety & Security Report, dated October 2026 and 217 pages long. A text search of it finds no mention of Carbon, and none of SEC-bench Pro or ExploitGym. Its CWE-bench section is about Argon’s 68%. So for two of Carbon’s three security records, the post is the whole published method.
What would make the records checkable
None of this says Carbon is weak at security work. A 71% on a held-out audit-and-patch set is a strong result, and Google is putting the model in front of defenders first, which is where a security-capable model is most useful. But the post presents three records in one breath, and they rest on three very different kinds of evidence.
The fix is cheap and has been asked of the field for years. In 2023 a group of sixteen researchers, two of them at DeepMind, argued in Science that aggregate metrics and lack of access to results limit our understanding of what AI systems can do. For Carbon, publishing the results would mean submitting to the SEC-bench Pro board, posting ExploitGym results in the benchmark’s own format, and shipping a Carbon section in the safety report. Until then, the CWE-bench row is the one I would quote.
References
- Kavukcuoglu, K. (2026). Introducing Gemini 4 Carbon. Google, 28 October 2026.
- Google DeepMind (2026). Gemini 4 Argon Safety & Security Report. October 2026, 217 pages. Linked from reference 1 as its “Safety and Security report.”
- SEC-bench (2026). SEC-bench Pro leaderboard. Overall board, read 29 October 2026; paper: SEC-bench Pro: Can Language Models Solve Long-Horizon Software Security Tasks?, arXiv:2605.26548, 26 May 2026.
- ExploitGym (2026). sunblaze-ucb/exploitgym. Repository, read 29 October 2026; paper: ExploitGym: Can AI Agents Turn Security Vulnerabilities into Real Attacks?, arXiv:2605.11086, 11 May 2026.
- Collinear (2026). CWE-bench v1 leaderboard. Read 29 October 2026.
- Burnell, R., Schellaert, W., Burden, J., Ullman, T. D. et al. (2023). Rethink reporting of evaluation results in AI. Science 380(6641), 136–138, 14 April 2023.
- Gautam Parab (2026). Gemini 4 Argon Is Held Back Over Cyber, and Its Results Table Has One Cyber Row. 30 September 2026.