Security Advisory — Lovable 2025/2026

Did your Lovable projects
expose credentials or sensitive data?

Lovable accidentally re-enabled access to chat histories on public projects after a backend permissions change. Because developers paste API keys, database URLs, and credentials into AI prompts, public chat histories are higher-risk than public code. Answer 4 questions to assess your exposure.

Exposure window: Feb 2026 (re-enabled after backend change)Root cause: Permissions unification re-enabled public chat accessFixed: Lovable reverted — all public project chats now private

This is a local self-assessment — no data is sent to our servers. Answers stay in your browser.

Self-audit checklist

Answer 4 questions to assess your exposure and get specific action items.

01
Did you use Lovable before December 2025?
December 2025 is when Lovable switched to private-by-default across all tiers.
02
Were any of your projects set to "Public" — or were you on the free tier before May 2025?
Free tier users could not create private projects before May 2025. All projects were public by default.
03
Did you paste API keys, tokens, database URLs, or other credentials into the chat?
This includes anything you shared to give the AI context — connection strings, API keys for integrations, service passwords.
04
Did your chats contain internal system details, user data references, or business-sensitive information?
Internal endpoint URLs, schema details, user identifiers, business logic, or anything you would not want public.

Background

01
The "public" confusion

Lovable's public/private toggle controlled the entire project - chat history, code, and build artifacts. Many users assumed "public" only meant their published app was visible, not the prompts they used to build it.

02
What chats contain

Vibe-coding prompts typically include API keys pasted for context, database URLs shared to explain errors, service credentials dropped in mid-session, and internal system details. This makes chat histories higher-risk than the generated code.

03
The backend re-exposure

A February 2026 backend change accidentally re-enabled access to public project chats. Two HackerOne reports were closed without escalation - the triage team read it as intended behavior based on old documentation.

04
Who was affected

Free tier users before May 2025 could not make projects private. Anyone on any tier who had projects set to public and pasted credentials into chats should assume those chats were accessible during the window.

Based on the Lovable public statement and our full incident analysis.