Back to blog
AI & LLMvibe codingCVE

Vibe Coding Security: Real CVEs Caused by Cursor, Lovable, Bolt, and Copilot in 2026

Published on 2026-03-258 min readFlorian

Vibe Coding: Generating Code Without Understanding It

The term "vibe coding" refers to the practice of generating entire applications via AI assistants (Cursor, Lovable, Bolt, Copilot) without deeply understanding the produced code. In 2026, it has become the dominant development mode for startups wanting a fast MVP.

The problem: these tools generate code that works, but is not secure by default. Studies show that 62% of AI-generated code contains at least one known vulnerability.

Systematic Vulnerability Categories

Insufficient Authentication

AI assistants often generate code with client-side-only authentication. The server trusts the JWT token without verifying backend permissions. Authentication middleware is present but does not protect all routes.

Missing Access Control

This is the most frequent problem. AI generates complete CRUD endpoints without checking that the user has the right to access the requested resource. A user can modify another user's data by changing the ID in the request.

Secrets Exposed in Client Code

Assistants insert API keys, Supabase tokens, and credentials directly into frontend code. The environment variable is used client-side with NEXT_PUBLIC_ without the developer understanding this makes the key public.

SQL and NoSQL Injection

Generated code sometimes uses string concatenation to build queries rather than parameterized queries. This is particularly common with dynamically constructed Supabase queries.

Missing RLS on Supabase

Lovable and Bolt generate Supabase applications with Row Level Security policies either absent or permissive. The default policy allows everything, and the AI does not restrict it.

Real Cases in 2026

Healthtech startup: application generated by Lovable, pushed to production in 3 days. No RLS on patient tables. 15,000 medical records accessible to any authenticated user.

B2B SaaS: API generated by Cursor with admin endpoints accessible without role verification. A standard user could create administrator accounts.

E-commerce: Bolt application with Stripe keys hardcoded in client code. Secret keys were exposed in the JavaScript bundle.

What Developers Must Verify

  • Every endpoint has server-side access control, not just middleware
  • API keys are never in client code (check the bundle with DevTools)
  • RLS is enabled and tested on every Supabase table
  • Queries are parameterized, not concatenated
  • A security audit is performed before production, not after
  • The CleanIssue Approach

    We specifically audit applications built with vibe coding. Our checklist covers the 15 most frequent vulnerabilities in AI-generated code. If your application was built with an AI assistant, a external review quickly reveals critical flaws.

    Related articles

    Three adjacent analyses to keep exploring the same attack surface.

    Sources

    Written by Florian
    Reviewed on 2026-03-25

    Editorial analysis based on official vendor, project, and regulator documentation.

    Related services

    If this topic maps to a real risk in your stack, these are the most relevant CleanIssue audits.

    Need an external review of your HR SaaS?

    Share your product, stack, and client context. We will come back with the right review scope.

    Discuss your audit