Skip to main content
LLM Security Database
Skip to research details
Back to research findings
LMVD-ID: b4001fcb
Paper published August 3, 2026
Entry analyzed August 13, 2026
Paper-reported evidence
Confidence: Source-linked

The LMVD-ID is an internal research identifier, not an official CVE identifier.

Repository-Level Coding Agent Vulnerability Detection Gaps

VulnGym measures whether coding agents can locate and explain repository-level security vulnerabilities from realistic advisory and source-code context. The benchmark contains 184 reviewed advisories, 408…

Read primary paperBibTeX citation

Paper-evaluated models(7)

DeepSeek V4 Flash, GLM 5.2, MiniMax-M3 +4 more
  • DeepSeek V4 Flash
  • GLM 5.2
  • MiniMax-M3
  • Qwen3.5-2B
  • Qwen3.5-4B
  • Qwen3.5-9B
  • Qwen3.5-27B

Description

VulnGym measures whether coding agents can locate and explain repository-level security vulnerabilities from realistic advisory and source-code context. The benchmark contains 184 reviewed advisories, 408 line-annotated vulnerability entries, and 23 repositories, with separate end-to-end detection and oracle-conditioned localization tasks.

Examples

Reproduce defensively against fixed benchmark repository snapshots using read-only file inspection, known advisory labels, line-level grading, and no exploit execution; see https://arxiv.org/html/2608.02001 (opens in a new tab).

Impact

On the benchmark’s hard subset, the strongest tested agent-model combination, OpenHands with DeepSeek-V4-Flash, reaches 22.58% advisory recall, 15.22% entry recall, and 11.63% edit similarity. The findings describe missed benchmark vulnerabilities, not proof that a deployed scanner always misses that fraction of real issues. The reported benchmark results are limited by repository selection, advisory context, line-matching tolerance, read-only tool restrictions, and oracle-conditioned subtasks.

Affected Systems

  • Claude Code, OpenHands, and MiniSWE coding-agent scaffolds under the paper’s evaluated configurations
  • Repository-level code-review, security-triage, advisory-localization, and vulnerability-trace workflows
  • Security analysis agents restricted to read-only repository-search and file-inspection commands

Mitigation Steps

  • Evaluate repository-level security tools against reviewed vulnerabilities with line-level labels and reproducible repository snapshots.
  • Report advisory recall, individual-entry recall, localization quality, and false positives as separate metrics.
  • Pair agent findings with static analysis, independent review, and targeted regression tests before asserting coverage.
  • Improve cross-file trace construction and security-sensitive data-flow reasoning rather than relying on isolated file summaries.
  • Retain expert review for high-risk repositories and treat oracle-conditioned subtask scores separately from end-to-end discovery.

Evidence

Research context and confidence

Evidence and verification
Paper-reported; independent reproduction is not documented.
Primary source plus a dedicated evidence section.
Severity
Not rated by this catalog.
Source and publication type
arXiv · Research preprint.
Peer-review status is not provided by this source.
Author and publication status
Author metadata is not stored; see the primary paper.
Threat model and attacker access
Not explicitly classified; consult the primary paper..
Related deployment categories
Agent workflows; Coding agents
Taxonomy labels only; paper-specific deployment prerequisites are not inferred.
Affected systems
Claude Code, OpenHands, and MiniSWE coding-agent scaffolds under the paper’s evaluated configurations Repository-level code-review, security-triage, advisory-localization, and vulnerability-trace workflows Security…

Research Paper

VulnGym: Benchmarking Coding Agents for Repository-Level Vulnerability Detection

Primary source: arXiv. Findings are reported by the cited research and have not been independently verified.

View Paper