AI Agent Benchmark Vulnerabilities

2026-05-14 · source · source ↗ · raw capture · wiki page

UC Berkeley RDI research demonstrating that eight major AI agent benchmarks can achieve near-perfect scores through exploitation rather than genuine capability.

The Central Problem

Benchmark scores drive critical decisions about model selection, investment funding, and research direction, yet the underlying evaluations contain systematic vulnerabilities. "The benchmarks we rely on to measure AI capability are themselves vulnerable to the very capabilities they claim to measure."

Real-World Evidence

Benchmark-Specific Exploits

Terminal-Bench (89 tasks)

Replaced /usr/bin/curl with a wrapper that trojaned the uvx binary, producing fake pytest output. 100% score.

SWE-bench Verified (500 tasks)

A simple pytest hook forced every test to report as passing. 100% score.

WebArena (812 tasks)

Navigated Chromium to file:// URLs containing task configurations with reference answers.

FieldWorkArena (890 tasks)

Validation checked only whether the final message came from an assistant, ignoring content. Sending "{}" achieved 100%.

OSWorld (369 tasks)

Downloaded gold reference files from public HuggingFace URLs embedded in task metadata.

GAIA (165 tasks)

Reference answers publicly available on HuggingFace. Scoring normalizer collapsed whitespace/punctuation.

CAR-bench

Hidden comments in agent responses biased LLM judges.

Seven Recurring Vulnerability Patterns

  1. Agent-Evaluator Isolation Failure
  2. Exposed Answer Keys
  3. Unsafe eval() Usage
  4. Unsanitized LLM Judge Inputs
  5. Weak String Matching
  6. Incomplete Evaluation Logic
  7. Trusting Untrusted Output

Main Conclusion

"Don't trust the number. Trust the methodology." The field has not yet adopted adversarial robustness as standard practice in benchmark development.

BenchJack Tool

Automated agent-based vulnerability scanner for benchmark evaluation code. Being prepared for public release.