Lovable Security Issues: A Timeline From CVE-2025-48757 to the Passport Number Leak, and What Still Depends on You
Apps built on Lovable have exposed data three times since 2025, most recently passport numbers and 200,000 chat messages. Here is every reported issue in order, what changed, and what is still your job.
Where Worldwide
On this page 9 sections
Apps built with the AI app builder Lovable have now been reported exposing data three separate times. In the latest case, researchers could read passport numbers, ticket buyers' payment details and more than 200,000 private chat messages straight from the apps' databases. If your company runs a customer portal, booking form or internal tool built on Lovable, Lovable's own terms say you are responsible for that app and the data in it, so the gaps below are yours to close.
This post lists every reported issue in order, what changed after each one, and what still depends on you.
Lovable security timeline at a glance
| Date | What was reported | What changed |
|---|---|---|
| March 20 to 21, 2025 | Researchers led by Matt Palmer find Lovable-built apps with weak Supabase row level security and email Lovable | Lovable confirms receipt on March 24 |
| April 14, 2025 | A Palantir engineer posts publicly about the same problem | Researchers start a 45-day disclosure window |
| April 24, 2025 | Lovable 2.0 ships with a security scan | Researchers say the scan only checks that a policy exists, not that it is correct |
| May 29 to 30, 2025 | Researchers publish their statement; CVE-2025-48757 is published | Lovable disputes the CVE |
| February 3 to April 20, 2026 | A Lovable regression lets any Lovable user with a link see chat history and source code of public projects | Lovable fixes it and makes current public projects private |
| April 28 to October 30, 2026 | Supabase stops exposing new tables automatically | Applies to new tables only |
| November 2, 2026 | Crissy Field and Handelsblatt report thousands of Lovable apps sending database records to anyone | The report does not describe Lovable's response |
What is CVE-2025-48757?
Most Lovable apps store their data in Supabase. The app's web page carries a public key that talks to the database directly. Row level security (RLS) is the rule set that decides which rows each visitor can see. If those rules are missing or too loose, that public key opens the whole table to anyone.
The CVE record says weak RLS policies in Lovable, through versions dated 2025-04-15, let remote attackers with no login read or write any table in generated sites. It is rated 9.3, critical. The record is tagged "disputed": Lovable's position is that each customer is responsible for protecting their own app's data.
The researchers checked the homepages of 1,645 projects from Lovable's showcase. They report that 170 of them, about 10.3%, had inadequate RLS, across 303 exposed endpoints. Exposed data included names, email addresses, phone numbers and API keys. On one site they say they could write a record marking a payment as "paid", getting around Stripe.
The April 2026 Lovable incident
This one was a platform bug, not a customer setting. In a post dated April 22, 2026, Lovable says backend regressions in February 2026 re-enabled access to chat history and source code on public projects. Between February 3 and April 20, 2026, any Lovable user with a project link could see them. Lovable says private projects and Lovable Cloud were never affected.
Lovable also says researcher reports sent through HackerOne were closed without escalation because its triage team was using outdated internal documentation. Its fixes: making all current public projects private (except official templates), redesigning project visibility, retraining triage, and reviewing which public projects were viewed by people other than their owners. It says it will contact affected owners directly.
What is not known: Lovable's post does not say how many projects were viewed, or whether secrets were in them. Some news reports say database credentials were exposed; Lovable has not confirmed that. If anyone pasted a key or password into a public project's chat or code, treat it as exposed.
Lovable passport leak: the November 2026 research
Crissy Field GmbH worked with the German business paper Handelsblatt, which published on November 2, 2026. The researchers found 159,041 Lovable projects in Common Crawl data collected from December 2025 to September 2026. Of those, 34,545 used Supabase, and 24,664 sent database records as soon as the page loaded, with no login.
With further read-only requests, they found email addresses in 10,560 tables across 7,403 of those 24,664 sites, about 30%. Examples in the report:
- A service provider: more than 1,000 identity document records, including passport numbers, expiry dates and nationalities
- A lifestyle forum: more than 80,000 profiles and more than 200,000 chat messages
- Event organizers and restaurants: tens of thousands of ticket and food-sales records, with phone numbers, postal addresses, payment information and ticket codes
- A property management company: AI-written summaries of internal emails about tenants, owners and partners
What is confirmed and what is not
- Confirmed: the researchers say they could read this data without logging in.
- Not confirmed: misuse. The report says, "We could not establish whether any of it had been misused."
- Not a breach rate: the researchers say the 30% figure "should therefore not be read as a confirmed data leak rate." The sample is not representative of all Lovable apps, and some emails may be public contacts or test data.
- Not covered: the report only looked at Supabase, not Lovable's own database features introduced in late 2025.
Is Lovable safe for business apps?
The tool can build working software fast. The pattern above is about what happens after: an app goes live holding customer data, and nobody checks who else can read it. Lovable's terms say you are responsible for the apps you build and deploy, and "solely responsible for reviewing, validating, and using any AI Output." Our view, said once: AI can write code, but a human must review it before it ships. We wrote about who keeps these apps running in AI Can Build Your App. Who Is Going to Keep It Running?.
For a company, the risk is not just embarrassment. Exposed passport numbers, payment details or tenant records can trigger breach notification duties, and the exposure may have been open for months.
How to check your Lovable app this week
| Check | How |
|---|---|
| List every Lovable app | Include side projects and internal tools; note who owns each one and which Supabase project it uses |
| Turn on RLS for every table | In the Supabase dashboard, confirm each table in the public schema has row level security enabled |
| Read the policies | A policy that lets the anon role read everything is no better than none |
| Test as a stranger | Open the app logged out, open browser developer tools, and watch the Network tab for database records arriving on page load |
| Rotate exposed secrets | Any key or password in a public Lovable project before April 20, 2026, or in front-end code, should be replaced |
| Check project visibility | Confirm Lovable projects are private unless you mean to share them |
| Know the Supabase change | From October 30, 2026, new tables need explicit grants; existing tables keep their current access, so old exposures stay open until you fix them |
| Collect less | If the app does not need passport numbers or full payment details, stop storing them |
If you find real exposure, talk to your lawyer about notification obligations before deleting logs.
Lovable security questions people are asking
Is Lovable safe to use?
It can be, if someone reviews the database rules and tests the live app before real customer data goes in. Lovable's terms put that responsibility on you.
What is CVE-2025-48757?
A critical (9.3) record for weak row level security in Lovable-generated apps that let anyone read or write database tables. Lovable disputes it.
Was my Lovable app affected by the April 2026 incident?
Only public projects were affected, between February 3 and April 20, 2026. Lovable says it will contact affected owners directly.
Was data from Lovable apps stolen?
Not confirmed. The researchers say they could not establish whether the data was misused.
Who is responsible for security in a Lovable app?
The customer. Lovable's terms say you are responsible for the apps you build and deploy and for reviewing AI output.
Does the Supabase change fix exposed tables?
No. It changes how new tables are exposed. Existing tables keep their current grants, and RLS still has to be set up yourself.
The bigger lesson
Each of these issues was found by outside researchers, not by the app owners. Building fast is fine. Shipping without someone checking who can read the data is the part that keeps going wrong. For more on checking a live site, see Your Website Is Live. Can Anyone Find It, and Is It Locked?
Want a second set of eyes on your app or database? See security hardening or get a free quote.
Get security alerts like this by email, plus our free checklist, at /security-alerts.
Sources: Crissy Field: Lovable research; CVE record CVE-2025-48757; Matt Palmer: Statement on CVE-2025-48757; Lovable: Our response to the April 2026 incident; Supabase changelog: tables not exposed automatically; Lovable Terms.
Have a question about this article?
Ask it here and we will answer you directly by email. Questions are private, never posted.
Security alerts by email
Hear about the next one first.
When attackers start using a flaw in software businesses run on, we email what it is, whether it touches you and what to do that week, with a round-up of our latest security writing. Free, one-click unsubscribe. You get the checklist straight away: 12 things to secure this week.
Want a result like this?
Security alerts, breaches and the technology a business runs on: what happened, who it affects and what to do.
Get a Tech QuoteKeep reading
Mittwald MCP Server Breach: An Attacker Used a Web Host's AI Assistant Connector to Compromise 56 Customer Projects, What Is Confirmed and What to Check
German web host Mittwald says an attacker got in through the MCP server customers use to connect AI assistants...
Nitori Data Breach: Up to 37.62 Million Records May Have Leaked, What Is Confirmed and What Businesses Should Check
Nitori Holdings says up to 37.62 million records of personal information may have leaked after a break-in conf...
Sega Data Breach: 2.2 Million Email Addresses Leaked Through Email Vendor Arara, What Is Confirmed and What to Check
Sega says 2,196,044 newsletter email addresses leaked in a breach at its email vendor Arara, whose total has g...
