Not verified
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.
2026-04
Finding
What the outside of the app reveals
Anyone can see this from a browser. It is listed so you know what is on show.
Last updated September 20, 2026
Good to know · About ten minutes
Why AI-built apps get this
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.
What it affects
Anyone can see this from a browser. It is listed so you know what is on show.
What the evidence line looks like
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.
The fix
Nothing to do unless something here is a surprise to you.
Prompt for your coding agent
Review what the public pages reveal about the tools behind the app.
A result gives you this prompt written for your builder, in its own dialect, and a batch prompt that carries every fix at once.
Incidents that involved this
- Declared
CVE growth in AI-generated code
CVE entries attributed to AI-generated code rose from 6 in January 2026 to more than 35 in March 2026.
2026-03 - Observed
5,600 vibe-coded apps scanned
More than 2,000 vulnerabilities and more than 400 exposed secrets found across vibe-coded apps.
2026-02 - Not verified
Tenzai study of AI-built apps
69 vulnerabilities across 15 apps built by five AI coding tools.
2026-02
Related terms
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