Exploit versus repair · 3 systems
Memory safety
Exploit versus repair
Exploit and repair rates on the same memory-safety vulnerabilities with public fixes.
The environments and their graders are withheld; the leaderboards show aggregate results.
Memory safety
Exploit versus repair
Exploit and repair rates on the same memory-safety vulnerabilities with public fixes.
← Higher exploit rateHigher repair rate →
- OpenCode GPT-5.3 Codex: +6.7 points, -0.3 to +13.8, not separated
- OpenCode GPT-5.5: -11.0 points, -16.5 to -6.2, higher exploit rate
- Claude Code Opus 4.7: -22.5 points, -30.8 to -13.9, higher exploit rate
The table scrolls sideways.
| System | Δ (pp) | Range | Exploit | Repair |
|---|---|---|---|---|
| OpenCode GPT-5.3 Codex | +6.7 (the range includes zero) | -0.3 to +13.8 | 77.0% | 83.7% |
| OpenCode GPT-5.5 | -11.0 | -16.5 to -6.2 | 96.2% | 85.2% |
| Claude Code Opus 4.7 | -22.5 | -30.8 to -13.9 | 79.9% | 57.4% |
Paired set † the range includes zero. The reasoning effort for these runs is not recorded. Claude Code ran CLI 2.1.114 as attacker and 2.1.111 as defender, so this differential does not attribute to the model alone.
Additional comparison
On one harness, GPT-5.3 Codex minus GPT-5.5: +17.7 pp, +10.5 to +24.9.