← All advisories
VV-044highData leakage2026-04-20

Lovable bug exposed public projects’ code and AI chats

From 3 February to 20 April 2026, a Lovable permissions regression let any Lovable user with a project link read the source code and AI chat history of public projects. Lovable confirmed it and fixed it within two hours of the public report.

01.

What it is

Lovable: “Between February 3, 2026 and April 20, 2026 public project chat history and source code could potentially be accessed by any Lovable user provided they had a project link.” Backend regressions in February re-enabled access that Lovable had removed during 2025. Private projects and Lovable Cloud were not affected.

Researchers reported it through HackerOne from 22 February, but the reports were closed without reaching Lovable because the triage documentation still described public chats as intended behaviour.

The Register reports the researcher (@weezerOSINT) made five API calls from a free account to reach another user’s profile, public projects and source code, then pulled database credentials out of that code. Chats can include whatever users pasted in, such as API keys. Lovable’s first public response said “We did not suffer a data breach” before it apologised.

Lovable says it is making all existing public projects private, except its official templates, and reviewing which public projects were viewed by other users so it can contact their owners.

02.

How to check

  1. Did you have a Lovable project set to Public at any point between 3 February and 20 April 2026? Free-tier projects used to be public by default.
  2. Search that project’s chat history and code for anything you pasted in: Supabase service_role keys, database passwords, Stripe or OpenAI keys.
  3. Watch for an email from Lovable saying your public project was viewed by someone else.
03.

How to fix

  1. Rotate every credential that appeared in a public project’s code or chat, even if you think nobody looked.
  2. Keep secrets out of chat prompts and source. Store them as server-side secrets your backend or edge functions read at runtime.
  3. Check each project’s visibility. In Lovable, project visibility (who sees the editor, code and chat) is separate from who can visit the published app.
04.

Sources

More advisories for this tool
The weekly email

One email a week. Only what changed.

New advisories, CVEs and fixes for Lovable, Bolt, v0, Replit, Base44 and Cursor apps. No roundups of things you already read.

Free. The list is new, so the first issues go out once there are readers. Unsubscribe from any email in one click. We never sell or share addresses.