Devin
Security FAQ

What security issues do Devin AI apps have?

Get instant answers about your app's security.

Short Answer

The security issues specific to Devin AI apps are no human-in-the-loop for security decisions, exposed api endpoints, insecure dependency choices. These aren't generic — they map to how Devin AI deploys and what stack it leans on.

Detailed Answer

The specific issues we find in Devin AI apps

  1. **No Human-in-the-Loop for Security Decisions** — Devin makes architectural choices autonomously that have security implications.

2. **Exposed API Endpoints** — Autonomously created API routes may lack auth middleware.

3. **Insecure Dependency Choices** — Devin may install packages with known vulnerabilities.

4. **Missing Access Controls on Data** — Database tables and APIs may be accessible without authorization.

Why these are the issues specific to Devin AI

Devin AI apps ship with a recognizable stack (supabase, firebase, postgres). The issue list above is what appears when you scan that specific combination. A Firebase-backed app would have a different top-5; a self-hosted Postgres deployment would have yet another. Context is everything.

What VAS checks in a Devin AI scan

  • **Code Audit** — Review autonomously written code for security patterns.
  • **Dependency Check** — Scan installed packages for known vulnerabilities.
  • **Auth Verification** — Test all endpoints for proper authentication.
  • **Data Access** — Verify database access controls and data exposure.

Security Research & Statistics

10.3%

of Lovable applications (170 out of 1,645) had exposed user data in the CVE-2025-48757 incident

Source: CVE-2025-48757 security advisory

4.45 million USD

average cost of a data breach in 2023

Source: IBM Cost of a Data Breach Report 2023

500,000+

developers using vibe coding platforms like Lovable, Bolt, and Replit

Source: Combined platform statistics 2024-2025

Expert Perspectives

There's a new kind of coding I call 'vibe coding', where you fully give in to the vibes, embrace exponentials, and forget that the code even exists.

Andrej KarpathyFormer Tesla AI Director, OpenAI Co-founder

Vibe coding your way to a production codebase is clearly risky. Most of the work we do as software engineers involves evolving existing systems, where the quality and understandability of the underlying code is crucial.

Simon WillisonSecurity Researcher, Django Co-creator

Check Your Devin AI App's Security

VAS scans for all the security issues mentioned above. Get a comprehensive security report in minutes.

Get Starter Scan

More Questions About This Topic

Which Devin AI security issue is most dangerous?

No Human-in-the-Loop for Security Decisions. Devin makes architectural choices autonomously that have security implications. This is the highest-impact finding because it tends to expose the full dataset or grant lateral movement in one step.

Are these issues unique to Devin AI, or do they appear across platforms?

The patterns overlap with cursor, claude code, copilot — all vibe-coding platforms share the "AI-generated code prioritizes functionality over security" problem. But the *specific manifestation* differs per platform. An exposed Supabase anon key is structurally different from an exposed Firebase config, which is different from an exposed Postgres connection string. The right scan is platform-aware.

How do I see which of these issues my Devin AI app has?

Run a VAS scan against your deployed Devin AI app URL. It checks every issue in the list above, confirms each by actually probing (not just reading headers), and prioritizes by severity with copy-paste fixes. Most Devin AI app scans return results in 2–3 minutes.