lovable supabase app security

Your Lovable Supabase App Might Be Showing Its Database. Here’s the Free Fix.

TL;DR: Security researchers scanned 159,041 Lovable-built projects and found that 24,664 of the Lovable Supabase apps among them returned database records the moment the page loaded, with no login. The cause is misconfigured access rules on the database — not a flaw in Lovable itself. Lovable’s head of security has responded publicly, said “the actual blame falls on us”, and asked builders to do one thing: run the free scan and click Fix.

What the Lovable Supabase research found

A Hamburg security consultancy, Crissy Field, working with the German business paper Handelsblatt, used the public Common Crawl archive to identify 159,041 Lovable projects that were online between December 2025 and September 2026. Of those, 34,545 used Supabase as their database — and the study looked only at those, so a Lovable Supabase app is the specific thing under the microscope here.

24,664 of those Lovable Supabase apps sent database records to the browser the instant the page loaded, with no login and no interaction. Digging further, the researchers found email addresses in 10,560 tables across 7,403 sites.

Now the caveats, which matter and which most coverage has dropped. The researchers say plainly that data arriving on page load “is not a security issue: the data may be intended for public display” — a public menu or event list is supposed to be readable. They also warn that “the 30% figure should therefore not be read as a confirmed data leak rate”, that the Common Crawl sample is “not representative”, and that “we could not establish whether any of it had been misused”.

What they did download is still sobering: over 80,000 forum profiles with names, emails and dates of birth plus more than 200,000 chat messages; over 1,000 identity records including passport numbers; ticket and food-order records including payment information. No apps were named, and the access method was deliberately withheld.

What Lovable said

This is the part that changed over the weekend, and it’s unusual.

Lovable’s head of security answered in public, under his own name, in the Hacker News thread about the research. He opened with “Thanks to the Crissy Field team for their work” — then confirmed the cause: insufficient Row-Level Security on the database, “which is exactly what our scanning is built to catch”.

He went considerably further than most vendors would:

“if apps continue to expose the data, the actual blame falls on us”

and described engaging with the criticism as a way to “act on the feedback, accept the blame”. He also set out what’s coming: publish gates that block apps with critical findings “available to all tiers”, scheduled scans moving to all paid tiers, a new security interface “this month”, and — carefully worded — a possible path to act against apps that grossly violate privacy: “notification with ask to fix, grace period, if no action and no improvement – soft block until issues fixed”.

The disclosure itself was handled properly on both sides. The researcher wrote that Lovable “was informed weeks in advance”, provided an official statement confirming the findings, and “at no point did they ask us to delay publication or threaten legal action”.

Why this matters if you don’t write code

Row-Level Security is the single most important idea in this story, so here it is without jargon.

When your app stores data, the database doesn’t automatically know that Alice should see Alice’s orders and not Bob’s. Something has to tell it. Row-level security is that rule — written per table, saying who may read which rows. If nobody writes the rule, the database answers everyone the same way: with everything.

The trap for anyone building by describing what they want is that you are never asked. You say “add a sign-up form”, you get one, and a table appears to hold the entries. Nothing stops to ask who may read that table. It’s the same failure we wrote about when an attacker reached Bubble’s systems — and the same one Lovable itself named as its commonest scanner finding.

Lovable’s own explanation is partly generational: “a lot of projects mentioned in the research are created with older models”, and “building an insecure app is much harder today than 6-12 months ago”. That’s plausible and it’s also the point — a Lovable Supabase app you built months ago and forgot is exactly the one most likely to be affected, and it will not fix itself.

The free fix for your Lovable Supabase app

We wrote four days ago that Lovable’s security scan is free and most people have never run one. This research is what that sentence looks like at scale. So:

  1. Open every Lovable Supabase app you have published — including the ones you forgot. Those are the risky ones.
  2. Run the deep scan. It’s free on every tier, including Free, and it’s on demand.
  3. Click Fix on the findings. Lovable’s head of security’s exact ask was “click Free Fix and do not ignore warnings”.
  4. Turn on auto-fix in project settings if you’d rather not babysit it. He confirmed it’s available on the Free tier too.
  5. Check your email and in-app notifications. Lovable says its team would contact affected customers; several people in the thread said they’d heard nothing, so don’t wait to be told.

One honest caveat on auto-fix: he was candid that it’s hard to get right, noting that even 99% success “at the scale of 10M apps, it would mean breaking 100 000 apps”. Review a fix before you ship it on anything that matters.

Who should care

  • Building a revenue app: urgent if your Lovable Supabase app collects anything personal. Do it today.
  • An internal tool for your business: still worth scanning your Lovable Supabase app — “internal” often means “published with a link nobody guards”.
  • A website or landing page: low risk if it holds no user data. Check whether a form quietly created a table.
  • Learning: the best possible lesson, learned free rather than expensively.
  • No idea yet: this is the honest cost of building without code, and it’s manageable — but only if you look.

Not sure which you are? The 60-second Tool Finder quiz sorts it in a minute.

Our take

We’d give Lovable real credit for the response. Answering under your own name, thanking the researchers, and saying the blame falls on you is not the standard playbook, and the commitments came with timeframes rather than vagueness.

The harder question, raised repeatedly by builders in that thread, is whether a tool sold on not needing technical knowledge can fairly leave database permissions to the person who was told they didn’t need to understand databases. Free scanners and an auto-fix button are a good answer. Secure-by-default would be a better one — and the promised publish gates on critical findings, for every tier, are the closest thing to it.

Until those ship: the scan is free, it takes minutes, and the Lovable Supabase app you forgot about is the one to check first.

Some links on this page are affiliate links. If you buy through them we may earn a commission at no extra cost to you.

FAQ

Is my Lovable Supabase app affected?

Only a scan will tell you. The research covered projects published between December 2025 and September 2026 that used Supabase, and the researchers stress their sample isn’t representative. Run Lovable’s free deep scan on every app you’ve published, starting with the oldest.

Was this a hack or a breach of Lovable?

Neither, on the evidence published. The researchers describe misconfigured access rules in individual Lovable Supabase apps, not a flaw in Lovable’s platform, and say they could not establish whether any data was misused. Lovable’s head of security identified the cause as insufficient row-level security in those apps.

Does the fix cost anything?

No. Lovable’s head of security confirmed the automatic pre-publish scan and the deeper on-demand scan are free on all tiers, including the Free plan, and that auto-fix is available there too. Scheduled scans are described as moving to all paid tiers soon.

Similar Posts