Tens of thousands of apps built with the AI coding platform Lovable were quietly exposing their users' private data to anyone who opened them, according to a security report published on November 14. No hacking was involved: the databases behind the apps were simply readable by any visitor.

German application-security firm Crissy Field, working with the business daily Handelsblatt, scanned 159,041 Lovable projects found in the Common Crawl archive between December 2025 and September 2026. Of those, 34,545 used Supabase as their database — and 24,664 of them, about 71 percent, sent database records straight to a visitor's browser the moment the page loaded, before any login or click.

What the researchers found

The exposed data was not test filler. At one service provider, more than 1,000 identity-document records were readable, including passport numbers, expiry dates and nationalities. A German lifestyle forum built on Lovable exposed more than 80,000 user profiles — names, email addresses, birth dates and gender — alongside more than 200,000 private chat messages.

Email addresses turned out to be the easiest marker of exposure: records containing them appeared in 10,560 tables across 7,403 sites. The researchers stress that this is not a confirmed leak rate — public contact addresses and test data get counted too, while personal records without an email get missed — but the scale of readable data was unambiguous. The researchers used only read-only requests with the public access key every Lovable frontend already ships to the browser, and they did not download complete datasets, so the real exposure is likely worse than what they measured.

Why the databases were open

The root cause is a default setting. Supabase databases ship with row-level security — the mechanism that controls which records each user may read or change — switched off unless a developer explicitly turns it on and writes access policies for it. Lovable's AI code generator built working apps without ever asking whether the data should be public, and many of the people building with it have no security background.

That combination is what made the exposure so widespread. A website can show a login screen while the database behind it still answers requests for private records from anyone. Lovable's own documentation tells builders to review and test the rules governing that access before publishing — but nothing in the building flow forced them to.

What Lovable said, and what happens next

Lovable characterised the issue as a wider configuration problem involving Supabase, according to Cybernews, rather than a breach of its own platform. The researchers agree on that point: the report does not allege that anyone hacked Lovable, and the firm says it could not establish whether anyone misused the exposed information, how many people were affected, or whether the access has since been closed.

The researchers recommend that a named person with security expertise review access permissions before any app handles confidential data — and re-check them after every significant change. The findings struck a nerve beyond the security community: the story reached number one on Hacker News, with more than 700 points and nearly 300 comments debating where the blame sits — with Lovable, with Supabase, or with builders who never knew the question existed.

For a platform valued at $6.6 billion with eight million users, the episode is a warning about the new shape of software risk. Vibe coding can ship a working product in an afternoon, but a database that answers the whole internet was never a feature anyone asked for — and the people whose passports and private messages were readable never consented to it.