Cybersecurity
Teknosfera Newsroom
Cybersecurity

Lovable's leaks show the real cost of vibe coding: nobody owns security

Passports and 200,000 chat messages sat open on apps built with Lovable. Platforms that promise no technical knowledge is needed must make secure defaults the product itself.

Published
November 15, 2026
Reading time
3 min
Categories
Cybersecurity

AI-generated image

If a platform tells you that you need no technical knowledge to build an app, who is supposed to lock the door? That is the uncomfortable question behind the latest Lovable story, and the honest answer today is: nobody in particular.

The facts, per research by the German security firm Crissy Field, done with Handelsblatt: the team analyzed 159,041 Lovable projects online between December 2025 and September 2026, using Common Crawl data. Of the 34,545 that used the Supabase database service, 24,664 sent database records on load with no login. Among the examples they cite are a German lifestyle forum with more than 80,000 profiles and over 200,000 chat messages accessible, and a service provider exposing more than 1,000 records with passport numbers, expiration dates and nationalities. The researchers could not establish whether any of it was misused.

The marketing says no expertise needed, the contract says your problem

The most revealing detail is not technical. Crissy Field notes that Lovable repeatedly stresses that no technical knowledge is needed, while its Terms & Conditions put responsibility for applications and data handling on customers. In our view, that is the whole scandal in two sentences. You cannot sell a product to people who can't audit access rules and then hand them the liability for access rules.

To be fair, the researchers are careful. Access control mistakes happen in human-written apps too. Their 30% figure (7,403 of the 24,664 sites with email-bearing records) is explicitly not a confirmed leak rate, since public contact addresses and test data count, and the Common Crawl sample isn't representative of all Lovable apps. Some of that data may be meant to be public. So this is not "30% of Lovable apps leak." But the individual cases, passports included, need no statistics to be damning.

Templates make bugs scalable

What worries us more than any single leak is the pattern. Crissy Field points out that Lovable's database integrations follow recurring patterns, so an approach that works against one app may work against many with little extra effort. We think that is the dark side of generation: the same assistant that writes your app can write thousands of near-identical ones, and one flawed habit can become an industrial-scale vulnerability.

Human developers tend to make idiosyncratic mistakes. A generator makes consistent ones. Attackers love consistency.

Secure by default has to be the product

The researchers' advice is sensible: get an expert review of permissions before handling confidential data, and don't treat automated checks as a substitute for a professional assessment. But telling a first-time founder to hire a security consultant is telling them not to use the product as advertised. It's a disclaimer, not a fix.

What would a real fix look like? It's our opinion, not something the documentation says Lovable plans: tables private until the builder explicitly makes them public; a loud, blocking warning when a table holding emails, IDs or payment fields is readable without authentication; and a pre-publish check that refuses to ship the dangerous configuration. If the platform generates the database wiring, it owns the default. Anything less is shipping the footgun and blaming the user for pulling the trigger.

Note too the irony flagged by Cybernews: around the time of the findings, Lovable's CEO Anton Osika told CNBC that AI was collapsing barriers to starting a business. It is. The barrier to starting has fallen; the barrier to handling other people's passports responsibly has not moved an inch.

What to do now

If you build with these tools: assume nothing is protected until you've tested it logged out, and don't collect identity documents or payment data in a weekend project. If you run a platform like this: stop treating security as the customer's chore. The vibe-coding bill is arriving, and right now the people paying it are the ones whose passport numbers were never part of the deal.

Debate topics

No topics yet: start the first one.

More stories