What the researchers found

Crissy Field, a security firm in Hamburg, published a report on 14 November 2026 about apps built on Lovable, the AI coding platform. Handelsblatt had covered an earlier version of the findings on 2 November.

The researchers analysed 159,041 Lovable projects from December 2025 to September 2026. Of the 34,545 that used the Supabase database service, 24,664 websites sent database records to the browser on load, with no login needed. One German lifestyle forum exposed more than 80,000 profiles and more than 200,000 chat messages. A service provider exposed more than 1,000 records with identity document details, including passport numbers, expiry dates and nationalities.

The report puts the cause down to access control mistakes in the database integrations. It also says that finding email addresses in 7,403 sites is not a confirmed leak rate. I will stick to what they confirmed.

The excitement around it

The claim behind vibe coding is that anyone can now describe an app and get working software. That part is true. The gap between an idea and something running has collapsed.

So the first question is what that gap was hiding. A working app and a safe app look identical on screen. The forum members could log in, chat and see their profiles. Nothing looked broken, because the failure sat in who else could read the database.

Why a prompt doesn’t carry security

When you prompt a tool, you describe what the app should do. You rarely describe who must never see what. That is context, and it lives in your head and your experience. Alignment, strategy, approach and security all need that back-and-forth with someone who knows the situation. You don’t get it from a single prompt.

The platform can’t supply it either. It builds what you asked for. The researchers’ own advice says the same thing. They recommend expert review of access permissions before apps handle confidential data, and repeated checks after significant changes. They also say automated checks don’t replace a professional security assessment.

Where vibe coding is genuinely useful

Personal tools are where the shift is real. A normal person can now build fairly competent software for their own use. I replace many tools and scripts with ones I build myself this way.

The fallout is small because the tool only handles my own data. If I get the permissions wrong, I have exposed my own notes to myself. Nobody else’s passport sits in that database.

Consumer utilities will feel this shift the most, since many of them are now easy to build yourself. That is a real change, and I don’t dismiss it.

What changes when the data belongs to someone else

Take a clinic that wants a booking and intake app for patients. Or a travel service that collects passport details for bookings. Or a shop that builds its own customer portal. Each one can now get a working version in an afternoon.

The moment real customers type their details in, the risk changes. You are responsible for every output that leaves your hands, and that includes what your app shows to strangers. The service provider in the report was probably not careless on purpose. It likely had an app that worked and no one whose job was to ask who could read the records.

Speed was never the hard part of this. Reviewing the build before launch is, and it needs a person.

What a business should do

If you build for yourself, build freely. Keep the tool on your own data, and don’t put customer records into it as a shortcut.

If you build for customers, do these things before launch:

  • Name one person who is responsible for how the app protects customer data. A named person, not “the team”.
  • Have that person, or a qualified security reviewer, check the access permissions on the database. Test it from outside, with no login, to see what comes back.
  • Collect only what you need. If you don’t need passport numbers, don’t ask for them.
  • Repeat the review after every significant change, as the researchers advise.
  • If you can’t do the review, buy a tested product for that job instead of building it.

Source: Crissy Field: Lovable: Many Apps Built on the Platform Expose Sensitive Data