First-quarter 2026 assessment of 200 apps
183 of 200 vibe-coded apps, 91.5 percent, contained at least one vulnerability traceable to AI hallucination or missing security context.
Finding
Card processors expect a stated refund position, and disputes are harder to answer without one.
This week · An afternoon
Legal pages get postponed until the day a payment provider asks for them. Then they arrive as a template that mentions a company that is not yours. A real privacy, terms and refunds page for this specific app is a launch requirement, not paperwork for later.
Card processors expect a stated refund position, and disputes are harder to answer without one.
no link to a privacy page found in the footer of https://example.com
Every finding on a result carries a line like this one: the request that was made and the answer that came back. You can run the same request yourself and get the same answer, which is the point.
Write a short refund page stating the window and the process, then link it from the footer.
Prompt for your coding agent
Create a real refund policy page at /refunds and link it from the footer on every page. It must cover which purchases are refundable, the time window, and how to request one, written for this specific app with no placeholder text and no lorem ipsum.
A result gives you this prompt written for your builder, in its own dialect, and a batch prompt that carries every fix at once.
183 of 200 vibe-coded apps, 91.5 percent, contained at least one vulnerability traceable to AI hallucination or missing security context.
CVE entries attributed to AI-generated code rose from 6 in January 2026 to more than 35 in March 2026.
More than 2,000 vulnerabilities and more than 400 exposed secrets found across vibe-coded apps.
69 vulnerabilities across 15 apps built by five AI coding tools.
Run the free Launch Risk Check on your app
ShipReady is not a penetration test or a security certification. No automated check can prove an application is secure.
Last updated September 20, 2026