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
Naming the exact version tells anyone scanning the internet which known issues to try first against your host.
This week · About ten minutes
Builders leave traces: a header, a build artefact, a familiar path, a meta tag nobody removed. On its own a fingerprint is harmless. It becomes useful to someone else when a class of issue is reported against a particular builder and they want a list of apps to try it on.
Naming the exact version tells anyone scanning the internet which known issues to try first against your host.
x-powered-by: Express, build artefact names the framework
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.
Remove or shorten the Server and X-Powered-By headers in your hosting settings. Observed: {value}.
Prompt for your coding agent
Your responses announce the server software ({value}). Remove or shorten the Server and X-Powered-By headers in your server or hosting settings.
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