Reported in recent model launches
These model reports include this benchmark. Their harnesses, task subsets, scoring policies, and resource budgets can differ; follow each report’s evaluation notes before joining the numbers.
What it measures
A controlled security evaluation measures model capability on vulnerability-related software tasks.
How to read the result
For defensive capability assessment, retain the exact dataset, safeguards, task budget, and success definition behind the reported aggregate.
Limits and comparison traps
Different release windows and score definitions appear in launch reports. Results describe a contained evaluation and do not establish safe autonomous operation.
Epoch data and evaluation setting
Epoch AI publishes this benchmark in its capability collection. Imported rows retain the published score column and model configuration. Original authors and evaluation providers remain credited in the result references.
Epoch attribution and score coverage
Data is attributed to Epoch AI under CC BY 4.0, with original evaluation providers credited in the linked source snapshots. Scores are imported only where a published mapping identifies the field and its scale; missing or incompatible records are omitted rather than assigned zero.
Published evaluation
Exact values from the publisher’s embedded full comparison table. Maximum effort, fallback settings and dated model versions remain in model labels. Blank cells stay missing. Source footnotes specify mixed harnesses and externally quoted comparisons; this is a launch-reported cohort rather than a new independent evaluation.
Where this fits in an evaluation suite
The agent wrapper is part of the system. Pin tools, dependencies, timeouts, tests, and the repository revision. Compare contest coding separately from repository maintenance.
Start with a capability hypothesis, then choose a second test with a different failure mode. Keep the checkpoint, reasoning effort, agent tools, sampling policy, and scoring procedure fixed when measuring a training intervention. Record failures and missing outputs in the denominator.
A reproducible comparison
Exact values from the publisher’s embedded full comparison table. Maximum effort, fallback settings and dated model versions remain in model labels. Blank cells stay missing. Source footnotes specify mixed harnesses and externally quoted comparisons; this is a launch-reported cohort rather than a new independent evaluation.
Publish the exact run configuration, item coverage, score units, and available uncertainty. If a source supplies only an aggregate or a single run, preserve that limit. A new model name or a rounded score alone does not establish a capability improvement.
PRIMARY EVIDENCE & FURTHER READING
- Introducing Kimi K3.1 Pro ↗
- GPT-6 Astra: A new generation of intelligence ↗
- ExploitBench v0.1 ↗
- Capabilities & benchmarking — retained external evaluation records ↗
Reviewed 2026-10-27. Explanation and interpretation by RLTasks. Benchmark ownership remains with its original authors.