VICBench: A Multi-Language Benchmark for Code Vulnerability Detection
Evaluating security vulnerability detection tools requires benchmark datasets with vulnerability-inducing commits (VICs) - the commits that first introduce vulnerabilities into codebases. VICs are essential for determining the full range of vulnerable software versions. Existing vulnerability datasets suffer from limited programming language coverage, restricted patch complexity, and narrow project scope. Through our dual annotation by human experts and an agentic workflow, we create a benchmark
Record details
Published: 12 August 2026
Source: arXiv cs.AI
Category: Research
Topics: Agents & autonomy
Retrieved: 13 August 2026
Related evidence
These records share source-supplied organisations, an exact publisher byline, automatic topics or regions. The reason is shown on every link; related does not mean supporting, agreeing with or verifying this record.
An Agentic Workflow for Legacy HPC Modernization: Converting the Two-Electron-Integral Core of GAMESS
arXiv cs.AI · 12 August 2026
One Frozen Simulator Is Not Enough: Simulator Collapse in Multi-Agent RL
arXiv cs.AI · 12 August 2026
AI isn’t ready to research itself
Nature Machine Intelligence · 12 August 2026
Convergent Detour Hijacking: Task-Preserving Resource Amplification in Skill-Based LLM Agents
arXiv · 12 August 2026
"Pharos Night: Crown Pursuit": An AI-Native Deck-Building and Tactical Arena Game Design Based on Multi-Agent Systems
arXiv cs.HC · 12 August 2026
VAKRA: Evaluating Multi-Hop Reasoning Across APIs and Retrieval Under Tool-Use Policies
arXiv cs.AI · 12 August 2026
How to cite this record
ethics.ai (12 August 2026), “VICBench: A Multi-Language Benchmark for Code Vulnerability Detection,” evidence record 19028, https://ethics.ai/record/19028 (originally published by arXiv cs.AI).
Use and limitations
This page is a stable index and citation surface for a source record. ethics.ai did not author the underlying report and has not independently verified every claim. Automatic topics may be imperfect. For consequential use, quote and cite the original publisher.