Papers › Cybench: A Framework for Evaluating Cybersecurity Capabilities and Risks of Language Models

Cybench: A Framework for Evaluating Cybersecurity Capabilities and Risks of Language Models

15 Aug 2024arXiv:2408.08926archive 2025-07-28

Andy K. Zhang, Neil Perry, Riya Dulepet, Joey Ji, Celeste Menders, Justin W. Lin, Eliot Jones, Gashon Hussein, Samantha Liu, Donovan Jasper, Pura Peetathawatchai, Ari Glenn, Vikram Sivashankar, Daniel Zamoshchin, Leo Glikbarg, Derek Askaryar, Mike Yang, Teddy Zhang, Rishi Alluri, Nathan Tran, Rinnara Sangpisit, Polycarpos Yiorkadjis, Kenny Osele, Gautham Raghupathi, Dan Boneh, Daniel E. Ho, Percy Liang

Language Model (LM) agents for cybersecurity that are capable of autonomously identifying vulnerabilities and executing exploits have potential to cause real-world impact. Policymakers, model providers, and researchers in the AI and cybersecurity communities are interested in quantifying the capabilities of such agents to help mitigate cyberrisk and investigate opportunities for penetration testing. Toward that end, we introduce Cybench, a framework for specifying cybersecurity tasks and evaluating agents on those tasks. We include 40 professional-level Capture the Flag (CTF) tasks from 4 distinct CTF competitions, chosen to be recent, meaningful, and spanning a wide range of difficulties. Each task includes its own description, starter files, and is initialized in an environment where an agent can execute commands and observe outputs. Since many tasks are beyond the capabilities of existing LM agents, we introduce subtasks for each task, which break down a task into intermediary steps for a more detailed evaluation. To evaluate agent capabilities, we construct a cybersecurity agent and evaluate 8 models: GPT-4o, OpenAI o1-preview, Claude 3 Opus, Claude 3.5 Sonnet, Mixtral 8x22b Instruct, Gemini 1.5 Pro, Llama 3 70B Chat, and Llama 3.1 405B Instruct. For the top performing models (GPT-4o and Claude 3.5 Sonnet), we further investigate performance across 4 agent scaffolds (structed bash, action-only, pseudoterminal, and web search). Without subtask guidance, agents leveraging Claude 3.5 Sonnet, GPT-4o, OpenAI o1-preview, and Claude 3 Opus successfully solved complete tasks that took human teams up to 11 minutes to solve. In comparison, the most difficult task took human teams 24 hours and 54 minutes to solve. All code and data are publicly available at https://cybench.github.io.

PaperPDFCodeCode Syntology ran

In Syntology Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, Syntology's MCP tool lists every function and class Syntology harvested from this paper and whether it ran (how to connect): get_harvested_code_for_paper(arxiv_id="2408.08926")

Code

Syntology Ran 10 of 10 code samples harvested from 2 repositories linked to this paper; 0 have no recorded run. Of those that ran: 1 ran · our draft was wrong; 9 ran with no contract checked.

By repository: official repository: 10 samples from 2 repositories, 10 ran. The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

andyzorigin/cybench officialmentioned in papermentioned on GitHub report
andyzorigin/cyber-bench officialmentioned in papermentioned on GitHubApache-2.0 report
princeton-pli/hal-harness mentioned on GitHub report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

10 samples harvested; 10 ran; 0 honoured the contract we drafted; 0 have no recorded run. Read from Syntology's graph 2026-09-24; that is when this build read the record, not when the samples ran.

1ran · our draft was wrong
9ran

Licence: 0 of the 10 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from 2 repositories linked to this paper, official or community; each sample names its own and says which. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself; “our draft was wrong” and “fixture could not drive it” are failures of Syntology's instrument, not of the code.

Each sample ends with its code_sha256, Syntology's identity for that exact code. An agent fetches the stored sample with Syntology's MCP tool get_code(code_sha256="…") (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples from a repository marked official are listed first. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of four reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; or the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar). Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

analyze_challenge_completion andyzorigin/cyber-bench/analytics/analyze_benchmark_run.py official repository ran Apache-2.0 (permissive) · a7e69c0c5022bb4f · report
analyze_completion andyzorigin/cyber-bench/analytics/analyze_benchmark_run.py official repository ran Apache-2.0 (permissive) · 4fe2313caf422564 · report
calculate_percentage andyzorigin/cyber-bench/grade_benchmark.py official repository ran Apache-2.0 (permissive) · 7b2dfc15a8b7acab · report
duration_to_seconds andyzorigin/cyber-bench/grading/guided_run.py official repository ran Apache-2.0 (permissive) · 9bcfded361d2b865 · report
duration_to_seconds andyzorigin/cyber-bench/grading/unguided_run.py official repository ran Apache-2.0 (permissive) · 7fb8980bde1da170 · report
load_data andyzorigin/cyber-bench/grade_benchmark.py official repository ran fingerprinted Apache-2.0 (permissive) · 3fd3e80df53a806b · report
load_list_from_file andyzorigin/cybench/run_benchmark.py official repository ran · our draft was wrong Apache-2.0 (permissive) · 80047d3cba4ac7d9 · report
read_fastest_solve_times andyzorigin/cyber-bench/analytics/analyze_benchmark_run.py official repository ran Apache-2.0 (permissive) · 433972f6b994dc8e · report
read_metadata andyzorigin/cyber-bench/run_task.py official repository ran Apache-2.0 (permissive) · 313007004d0ed238 · report
time_str_to_minutes andyzorigin/cyber-bench/grade_benchmark.py official repository ran Apache-2.0 (permissive) · 269b537229622374 · report

Datasets

Introduced by this paper, per the archive.

Cybench

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Cybench Claude 3.5 Sonnet Unguided Performance 17.5% #3 of 3 Archive leaderboard report

Ranks are positions in the archive's leaderboards as they stood at the 2025-07-28 snapshot. Results published since then are not among these rows, so a rank here is not a current standing.

Methods

LLaMA

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections