Backend
Threat Landscape of Vibe Coding and the Road to Secure Autonomy
arXiv cs.CR0 views
arXiv:2611.21822v1 Announce Type: new Abstract: Vibe coding is reshaping software development, enabling faster implementation and allowing individuals with limited programming experience to describe requirements in natural language while AI agents write, test, and deploy the code. As these agents evolve into autonomous systems that execute commands, manage dependencies, access cloud resources, and interact with other agents, their security risks extend beyond incorrect code to actions with direct consequences for software systems. Although research on these risks is expanding, it remains fragmented across areas including prompt injection, insecure code generation, supply-chain attacks, and human factors, with limited consensus on terminology, threat assumptions, and evaluation. This paper consolidates emerging research through the lens of the vibe coding workflow. We establish a reference architecture, characterise six levels of agent autonomy, and develop a threat model centred on five trust boundaries spanning developers, AI models, tools, cloud infrastructure, and the wider software ecosystem. Building on this foundation, we propose a taxonomy of twenty-one threats across nine classes. For each threat, we review the available evidence, assess proposed defences, and identify limitations. Our analysis highlights that risks increase with agents' operational authority, while most defences rely on model judgement and address isolated threats. Finally, we identify eleven research challenges, including enforceable limits on agent authority and shared benchmarks and methodologies for assessing vibe coding security.
Source:https://arxiv.org/abs/2611.21822PreviousLLMs as Validators for Cross-Chain Bridges: Evaluating Source-Level and Transaction-Level Attack Detection on SolanaNextBajillion: Cryptographic Clearing for Micropayments
Related posts

I had a CLI reminder tool (Gcal). I added English and a phone app on top. Here's how it went
0dev.to Go
Driving the Style: Velocity-Conditioned Whole-Body Control from Motion Demonstrations
0arXiv cs.RO
sqrtVINS-Based 360 Visual-Inertial SLAM Systems: Hilti-Trimble SLAM Challenge 2026 Entry
0arXiv cs.RO
Ontology-Compiled Control Barrier Functions for Heterogeneous Robot Teams
0arXiv cs.RO
I Used to Get Attached to My Code. I Don't Anymore.
0dev.to AI
Securing MCP Servers: Preventing Shadow Tool Declarations and JSON-RPC Parameter Poisoning
0dev.to AI