AI-Generated Code Accelerates Development but Expands Application Security Risk
Emerging Technology Risk · 5 sources · Updated 3mo ago · First seen Sep 3, 2026

Microsoft is expanding agentic software development across GitHub Copilot, Aspire, Windows development environments, WSL, and model-context-protocol integrations, with Distinguished Engineer David Fowler saying manual line-by-line coding is becoming less central. However, automated code generation continues to produce material security defects: Veracode’s 2026 benchmark found known vulnerabilities in roughly 44% of AI code-generation tasks, while Sonar’s evaluation of GPT-5.6 variants found higher bug and vulnerability densities than GPT-5.5 despite improved functional-task pass rates, including cryptographic misconfiguration, insecure resource handling, and concurrency flaws. Microsoft is deploying its MDASH agentic scanner across engineering environments to identify vulnerabilities at scale.
Security researchers also found exploitable weaknesses in rapidly built “vibe-coded” applications, including client-side-only authentication, browser-exposed API keys, permissive or missing Supabase Row-Level Security policies, and internet-exposed internal tools. Tests of GitHub Copilot’s GPT-4o recommendations showed proposed fixes for a Node.js path-traversal flaw could be bypassed by relative or URL-encoded traversal payloads. Organizations should require human architectural and security review of AI-produced changes and retain secure-by-default libraries, SAST, software-composition analysis, secret scanning, pull-request controls, backend secret management, and deny-by-default database access policies.


