The VibeSec Reckoning

martinfowler.com
May 27, 2026
14 min read
45/100
Summary
Vibe coding allows non-technical users to rapidly develop applications using generative AI tools, accelerating software prototyping. AI agents often recommend insecure configurations due to their tendency to prioritize ease of use, leading to systemic security vulnerabilities.
Key Takeaways
- Vibe coding allows non-technical users to rapidly develop applications using generative AI, but it often leads to insecure configurations due to AI's tendency to suggest the easiest solutions.
- A significant rise in attacks exploiting application vulnerabilities has been observed, with 44% year-on-year growth and 1 in 5 enterprise breaches attributed to AI-generated code.
- To mitigate security risks, organizations should implement a security context file, be cautious with AI permission requests, and establish a daily security intelligence feed.
- 25% of AI-generated code has confirmed vulnerabilities, highlighting the need for enhanced security measures in AI-assisted development.
Coverage & discussions
Hacker News · martinfowler.com
Community discussions
Historical count: 5 · 5 saved in sample · Historical sample
Analysis ready
Community Sentiment
Positives
- AI models are improving in areas like syntax resolution, indicating that foundational issues can be effectively addressed through training.
- The ability of AI to choose candidates based on a reward model shows promise in automating certain decision-making processes in software development.
- Many companies are successfully integrating AI into their coding processes, suggesting that AI can enhance developer productivity when used responsibly.
Concerns
- Current AI models struggle to write secure code, highlighting significant limitations in their training and application for security-critical tasks.
- There is a prevailing concern that relying on AI for coding could lead to negligence in security practices, as AI may not adequately identify vulnerabilities.
- The notion of using AI to automate critical engineering tasks without proper oversight is viewed as reckless and potentially harmful.
Related Articles

Eight Myths on Software Engineering and GenAI
Aug 4, 2026

Why Software Factories Fail (or: harness engineering is not enough)
Jul 23, 2026

The ways we contain Claude across products
Jun 4, 2026

The ladder is missing rungs – Engineering Progression When AI Ate the Middle
Mar 30, 2026

Vibe coding and agentic engineering are getting closer than I'd like
May 6, 2026