Vibe coding security: four times the code, ten times the bugs.

The productivity claims about AI coding assistants are real and measurable. So, it turns out, is the other half of the ledger — vibe coding security — and 2026 was the year enough code shipped for somebody to count it. None of this is an argument against the tools. It is an argument about who checks the output, and what happens when nobody does.

The two numbers that belong together

Across Fortune 50 engineering teams, developers using AI assistance produced commits at three to four times the rate of their peers, while the security findings coming from AI-generated code rose ten times over in six months, to more than 10,000 new findings a month by June 2025. Both halves are real. Put together they describe not a faster team but a team accumulating a particular kind of debt faster than it can be reviewed.

Nothing here says the code does not work. It says it works and is exploitable, which is a much harder failure to notice, because the thing you test for is whether the feature does its job. Cross-site scripting and log injection do not show up when the form submits correctly.

Why AI-generated code fails in this specific way

A model produces the most probable code for the request, and the most probable code on the internet is the tutorial version — the one that demonstrates a concept without the escaping, validation and parameterisation that production needs. Ask for a search box and you get a working search box, written the way search boxes are written in examples.

That is also why the failure rate is so uneven by language: Java came out worst at 71%, tracking the age and volume of the example code available for it. The model is not making a mistake by its own standards. It is reproducing the distribution it learned, and that distribution is mostly demonstrations.

What this means if you bought a cheap build

If a very low quote came with a very short timeline, it is worth knowing whether anyone reviewed the output for anything other than "does it look right". The visible layer — pages, forms, layout — is exactly the part AI does well, so a site can look entirely finished and carry a form that will accept a script tag.

The cheapest moment to find this is before launch; the most expensive is after a breach discloses it for you. A technical audit covers it directly, and what an AI-generated website actually gets you is the wider version of the same question.

What secure use of AI coding assistants looks like

The teams getting the productivity without the debt are doing three unglamorous things: automated security scanning in the pipeline so findings surface at commit rather than at audit, human review of anything touching input handling, authentication or data access, and an explicit rule that generated code is a draft. What tends to go wrong when none of that is in place, and what to check first, is the subject of what is vibe coding.

That is not a brake on AI, it is the condition under which the speed is worth having. We use these tools daily and hold the same rule internally — the reason we build with Next.js is partly that its defaults escape output by design, which removes an entire class of this problem before anyone types anything. The other half of the same year is that attackers adopted the same tooling, and faster — black hat hackers now run agent swarms is that story.

Sources

Checked September 2026. Controlled studies and disclosure counts — see the table footnote for what each does and does not measure.

• Veracode — Spring 2026 GenAI code security update ↗

  More than 150 large language models on security-sensitive tasks with no security guidance in the prompt: a 55% security pass rate, so about 45% of samples introduced an OWASP Top 10 flaw; 85% failed XSS defence, 87% log injection, Java worst at 71%. Model size made almost no difference, and the flagship 2026 releases were no better than earlier ones.

• Cloud Security Alliance — Vibe coding’s security debt: the AI-generated CVE surge ↗

  The CVE progression of 6 → 15 → 35 per month across January to March 2026, and the estimate that confirmed disclosures understate the real figure five- to tenfold.

• Apiiro — 4x Velocity, 10x Vulnerabilities ↗

  Tens of thousands of repositories and several thousand developers in Fortune 50 enterprises: AI-assisted developers produced three to four times as many commits, in fewer but larger pull requests, and by June 2025 AI-generated code was introducing more than 10,000 new security findings a month, ten times the December 2024 level.