mlsanityData to 7 Oct 2026

Trust but Verify? Uncovering the Security Debt of Autonomous Coding Agents

arXiv 2607.12428 ↗First posted 14 Jul 2026cs.CRcited by 0

On the map: LLM agents and tool use → Software engineering coding agents

Abstract (arXiv)

The increasing adoption of autonomous coding agents accelerates software development but also introduces scoped security risks within high-impact file paths that can outpace traditional human review capacity. While prior research has primarily evaluated these systems in terms of functional correctness and productivity, this paper presents a large-scale empirical study using the AIDev dataset to systematically characterize security code smells in agent-generated pull requests (PRs). Through a combination of a validated LLM-as-a-judge framework and manual qualitative analysis, we identify and classify security misconfigurations across 16,112 file changes spanning 4,022 pull requests. Our results reveal that 38.9% of agent-generated PRs contain at least one security smell, with supply chain integrity issues accounting for 82.3% of all detected security smells. Furthermore, hard-coded credentials constitute 99.6% of all critical-severity security smells. Crucially, we find that human collaborators are responsible for introducing 67.6% of genuine leaked secrets within these agent-assisted workflows, while existing automated and human review processes fail to detect 81.1% of these credentials prior to integration. These findings highlight substantial security risks in agent-assisted software development workflows and suggest a potential reduction in developer vigilance. They also underscore the urgent need for context-aware security guardrails implemented directly at the point of human-AI collaboration.

Key facts. No citing papers in the map yet (data through 7 Oct 2026). Placed in Software engineering coding agents, one of 16 directions in LLM agents and tool use. Builds on 10 of its 26 references that are in the map. First posted on arXiv 14 Jul 2026.

Builds on

10 of 26 references.

Closest ancestors · 4

Same direction, newest first

  1. 2026Understanding Dominant Themes in Reviewing Agentic AI-authored Code27 Jan
  2. 2026How AI Coding Agents Modify Code: A Large-Scale Study of GitHub Pull Requests24 Jan
  3. 2026Do Autonomous Agents Contribute Test Code? A Study of Tests in Agentic Pull Requests7 Jan
  4. 2025Agentic AI Software Engineers: Programming with Trust19 Feb

Other references · 6

  1. 2021Evaluating Large Language Models Trained on Codecited by 8,053
  2. 2023SWE-bench: Can Language Models Resolve Real-World GitHub Issues?cited by 3,193
  3. 2024Towards AI-Native Software Engineering (SE 3.0): A Vision and a Challenge Roadmapcited by 30
  4. 2025Good Vibrations? A Qualitative Study of Co-Creation, Communication, Flow, and Trust in Vibe Codingcited by 10
  5. 2026Artificial Intelligence in Open Source Software Engineering: A Foundation for Sustainabilitycited by 1
  6. 2026Testing with AI Agents: An Empirical Study of Test Generation Frequency, Quality, and Coveragecited by 1

Built on by

Not cited yet.

Similar, not cited

Close in wording, no citation either way

  1. 2026Security in the Age of AI Teammates: An Empirical Study of Agentic Pull Requests on GitHub
  2. 2026Not All Agents Are Equal: Code Quality and Post-Merge Maintenance Across Five Autonomous Coding Agents in the Wild
  3. 2026Insights into Security-Related AI-Generated Pull Requests
  4. 2026MOSAIC-Bench: Measuring Compositional Vulnerability Induction in Coding Agents
  5. 2026Why Agentic-PRs Get Rejected: A Comparative Study of Coding Agents
  6. 2026Detecting AI Coding Agents in Open Source: A Validated Multi-Method Census of 180 Million Repositories
  7. 2026Towards a Risk Assessment of Malicious Skill Files in Coding Agents
  8. 2026Coding with "Enemy": Can Human Developers Detect AI Agent Sabotage?