Sample alert How it works Coverage PENTEST METHODOLOGY DOCS PRICING FAQ MCP CONTACT LOG IN SCAN MY APP →

My Lovable project was public: what to check and rotate

FIX / PUBLIC LOVABLE PROJECT / 9 MIN READ

Treat every key in a Lovable project as exposed if the project was public between 3 February and 20 April 2026. This includes each key that you ever pasted into its chat or wrote into its code. Replace each one at its provider. Do this in order: database, payments, AI providers, email. Then redeploy and check the logs.

This guide shows how to check if your project was in scope and how to search the chat for keys. It also shows how to replace them and how to make the project private.

What happened to public Lovable projects?

Lovable published its own account on 22 April 2026 in its response to the April 2026 incident. Read it for the vendor view. This section lists what each side says.

What Lovable says:

  • A backend change in February 2026 “re-enabled public access to chat history and code on public projects.”
  • The window for this access ran from 3 February 2026 to 20 April 2026.
  • Any Lovable user with a project link could potentially read the chat history and source code.
  • Lovable shipped a fix on 20 April 2026, after a researcher made the issue public.
  • Private projects and Lovable Cloud were not affected.
  • It did not suffer a data breach. It calls the exposure a regression.

What the researcher says:

  • A free account could read source code, database credentials, and chat history of other users. The Next Web reports that this took as few as five API calls.
  • The researcher says the first report went to the bug bounty program on 3 March 2026. Lovable says the first report was on 22 February 2026.
  • The researcher says the fix covered new projects only. Lovable says its fix reverted the change for all public projects.

Where the two sides disagree:

  • Lovable denies a “data breach.” The researcher describes exposure of user data.
  • Lovable says public chats were intended behavior in the past, and the word “public” was unclear to many users.
  • Press reports differ on which projects were open. The Next Web says projects created before November 2025. Lovable says public projects in general.
  • Lovable has not published how many projects were read by people other than their owners. It says it is checking this and will contact the owners.

The Stack reports the same dispute. You cannot settle it from outside. Plan for the worst case.

How do I know if my project was in scope?

Your project was in scope if it had public visibility at any time from 3 February to 20 April 2026. Check what you can.

  1. Open the project in Lovable.
  2. Click Share in the top bar.
  3. Read the access setting. Lovable now shows Workspace, or Restricted on Business and Enterprise plans.
  4. Check your email for a message from Lovable. Lovable says it will tell owners of projects that other people viewed.
  5. Ask your team. A team member can have made a project public.

Lovable states that, from 22 April 2026, you cannot create public projects. It moved existing public projects to workspace visibility. A project that looks private today was possibly public in February.

Caution: If you cannot prove that the project was private for the whole window, assume it was public.

Remixing also matters. Lovable says that anyone who remixed a public project got the full chat history and source code. Remixing is now opt-in. Open the project settings and check the remix setting.

How do I search the chat history for keys?

The chat holds everything you typed to the agent. People paste keys to make a feature work. Search for them now.

  1. Open the project chat.
  2. Scroll from the first message to the last message. Read each message that you wrote.
  3. Use the browser search with these terms: key, secret, token, password, postgres://, sk_, eyJ.
  4. Copy each hit to a list. Write the service name next to it.
  5. Repeat for every project that was public. Include old test projects.

Look for these key types:

Pattern Service Risk
postgres://user:pass@host Database Full data access
eyJ... with service_role Supabase Bypasses RLS
sk_live_ Stripe Charges and refunds
sk- or sk-proj- OpenAI Cost and data
re_ Resend Email in your name
whsec_ Stripe webhook Fake payment events

The Supabase anon key is public by design. It is not a secret. The service_role key is a secret. If it appeared in a chat, read the service role key leak guide as well.

Also search the code. Open the files in the project, or in your GitHub repository. Search for the same terms. Check .env files, config files, and edge functions. In a local clone, this command lists likely hits:

git grep -nE "sk_live_|sk-proj-|whsec_|service_role|postgres://" $(git rev-list --all) | head -50

The command also searches the full git history. The GitHub secret alert guide shows how to read the alerts that GitHub sends for keys in a repository.

Warning: Do not paste the found keys into a new chat, a ticket, or a message to a colleague. Write the names of the keys only.

Pasted keys are not the only issue. The code of a public project could show your table names, your policies, your API routes, and your logic. An attacker can use this to plan an attack on the live app. Treat the app as known.

In what order do I replace the keys?

Replace the keys that cause the most damage first. Replace each key at the provider, not only in Lovable. A new value in Lovable does not make the old key stop working.

  1. Database. Replace the database password and the Supabase service_role key and JWT secret if they appeared.
  2. Payments. Roll the Stripe secret key and the webhook signing secret.
  3. AI providers. Create a new OpenAI or Anthropic key. Delete the old key.
  4. Email. Create a new Resend or Postmark key.
  5. Other keys. Replace the rest of the list.

For each key, do these steps in order:

  1. Create a new key at the provider. Keep the old key active for now.
  2. Put the new key in the Lovable Secrets view, or in your own environment.
  3. Publish the app again.
  4. Test the app. Sign in, load data, make a test payment.
  5. Delete the old key at the provider.

If you suspect abuse, skip step 1 and delete the old key first. A short outage is better than more abuse.

How do I replace Supabase keys?

Open the Supabase dashboard. Go to the project Settings. Open the API keys section. Create a new service_role key or secret key. Disable the legacy key after the app uses the new one. Read the Supabase API keys documentation for the current steps, because the dashboard changes.

To replace the database password, open Database settings and choose to reset the database password. Every client that connects with the old password stops working at once. Update each connection string first if you can.

How do I replace a Stripe key?

Open the Stripe Dashboard. Go to Developers, then API keys. Use Roll key on the secret key. Choose an expiry for the old key, for example 24 hours. Stripe keeps the old key alive until that time. Then update the value in your app.

For the webhook secret, open the webhook endpoint and roll the signing secret. Then update STRIPE_WEBHOOK_SECRET.

How do I replace an AI provider key?

Open the provider console. Create a new key with a clear name and, if the console allows it, a spend limit. Update the app. Delete the old key. Then check the usage page for spikes. The OpenAI bill spike guide lists what to look for.

How do I check if someone used the keys?

A key that leaked in a chat can be used for weeks. Check each service for use that you do not know.

What do I check in Supabase?

  1. Open the Supabase dashboard.
  2. Open Logs, then API Edge Logs.
  3. Set the time range to cover 3 February to now.
  4. Look for requests from IP addresses that you do not know.
  5. Look for many GET requests to large tables in a short time.
  6. Look for DELETE and PATCH requests that you did not start.

The log retention depends on your plan, so old events can be gone. Absence of events does not prove safety. Compare unknown IP addresses with your own address and your hosting provider.

Check the auth users table for new accounts that you do not know. Check the auth.users rows with a recent last_sign_in_at value from unusual places. The Supabase hacked guide has more checks.

What do I check at the other providers?

  • Stripe: Open Developers, then Logs. Look for API calls from IP addresses that you do not know. Check for refunds, new customers, and payouts you did not start.
  • OpenAI: Open the usage page. Compare the daily cost with the normal cost.
  • Resend: Open the logs. Look for emails that your app did not send.
  • GitHub: Open the repository Security tab and the audit log.

If you find use that you do not know, delete the key now. Then read the Lovable app hacked guide for the full response, and keep the logs.

How do I make the project private?

Do this after you replace the keys. A private project stops new readers. It does not remove copies that others already made.

  1. Open the project.
  2. Click Share.
  3. Select Workspace or Restricted access.
  4. Open Workspace settings, then Privacy & security, then Default project access.
  5. Set the default to Workspace.

Lovable says that all workspaces default to workspace access from December 2025. Before 6 November 2025, projects were public by default for free plans.

What can I do on the free plan?

The Lovable documentation lists Workspace as the default on all plans. It lists Restricted as a Business and Enterprise feature. So a free user can keep a project in the workspace and cannot use restricted access.

You can still reduce the risk on any plan:

  • Keep keys out of the chat. Use the Secrets view for each key.
  • Replace a key as soon as it appears in a chat.
  • Remove remix access if the setting is on.
  • Keep the code in a private GitHub repository. The GitHub repo guide shows how.

Project access does not control the published app. Anyone with the URL can open the published app unless you add a login. These are two different settings. Check both.

How do I stop this in the future?

Build the habit of a key list. Write down each key, the service, where it lives, and when you replaced it. Use a password manager, not the chat.

  1. Never paste a key into the chat. Tell the agent the name of the variable only.
  2. Use a key with the lowest rights that the feature needs.
  3. Set spend limits on AI provider keys.
  4. Keep a list of all keys by service and project.
  5. Put each key in one place only: the Secrets view or the server environment.
  6. Turn on secret scanning in the GitHub repository.
  7. Test the live app from outside each time you publish. Check RLS with the RLS checker.
  8. Read the project visibility setting each month. See the earlier Lovable BOLA report for a related case.

When should I get help?

Get help from a security engineer if one of these is true:

  • The logs show access from an address that you do not know.
  • Customer data, payment data, or health data was in the database.
  • You cannot tell which keys were in the chat.
  • The app made charges or sent email that you did not start.
  • You must tell users or a regulator.

Keep the logs, the key list, and the times of each action. A clear record saves time for the person who helps you.

Common questions

Did Lovable have a data breach?
Lovable says no. It says the access to chats and code on public projects was a regression that it fixed on 20 April 2026. A security researcher calls it a breach of user data.
Is a private project safe from this problem?
Lovable says that private projects and Lovable Cloud were not affected. The risk was for public projects. Keys in a private chat still need care, because chats are long-lived records.
Must I replace a key if I am not sure that someone read it?
Yes. Lovable does not give each owner a list of readers. A replaced key costs a few minutes. A used key can cost data and money.
Can I delete the chat history to remove the keys?
Deleting the chat does not make an old key safe. A copy can exist elsewhere. Replace the key at the provider, and then update the app.
Do I need to tell my users?
Check the law that applies to you. If the database held personal data and the logs show direct access, you can have a duty to tell users. Ask a lawyer if you are not sure.

Test what keys are open

A VibeEval scan tests the live app and the API of your Lovable project. It reports open database tables and keys in the browser code that a leaked key could reach.

14-day free trial · Cancel anytime

SCAN YOUR APP →