AI Risk Wire

Cases › security breach › LR-2026-0500

Lovable flaw exposed private project data, source code and credentials

Confirmed Why: 2 independent outlets · 2 independent reports

Developing: a major or severe case captured in the last 72 hours. Later changes are logged on the corrections page.

Status: no action reported

Severity major
Reported 20 Apr 2026
Developer and model Lovable
Industry AI app-building software development platform

No source states: loss or records, agent tool, could do, deployer.

Severity major: Test: unbounded scope stated. Fact: any free account holder can read every project created before the November 2025 cutoff.

Lovable, an AI app builder that generates code, provisions a backend and deploys applications for users, had an authorization flaw in its API. According to a security researcher, a free account could read the source code, database credentials, AI chat histories and live customer data of projects created before November 2025. The researcher showed real personal information from a Danish nonprofit's admin panel. Lovable was notified through its HackerOne programme on March 3, 2026, and added ownership checks only for projects created after the cutoff. The researcher disclosed the flaw publicly on 2026-04-20. Lovable said it did not suffer a data breach and described the exposure as a visibility-setting misunderstanding.

What happened

1 · What it was doingThe platform generated application code and provisioned backends from natural-language descriptions.
2 · What went wrongA missing ownership check let any free account read other users' projects created before November 2025.
3 · How it was caughtAn independent security researcher found and publicly disclosed the flaw.

What was done

No source states an action or fix.

Risks

Data leaked or sent out
Primary32 incidents

Read from the sources; not yet reviewed by a person.

Controls

Not yet read for controls. Controls that mitigate the primary risk:

Harness

Network egress control

Application

Sensitive-data checks on outbound data · Output filtering and redaction · Human approval for high-impact actions · Data minimisation · Least-privilege access for the agent · Activity logs

Evidence

No source states: what it reached or did, when it was found, how many records were exposed, the direct loss, a count of the other parties affected, any court case, what set it off, what was done.

Show the full account: 1 items from the primary sources

What happened, in order

  1. 2026-04-20 The researcher publicly disclosed the flaw.
Show every field, with its source and grade

The AI system

Developer
Lovable
C one secondary source states it
What it was for
Generates application code and provisions and deploys backends from natural-language descriptions
C one secondary source states it

What happened

Earliest source we hold
2026-04-20
D inferred by us from the described behaviour, reason shown
Who caught it
an independent researcher or journalist
C one secondary source states it
Cause
a shared system was the path
C one secondary source states it
Cause in detail
Missing ownership checks on API endpoints, including /projects/{id}, let users query project data that was not theirs
C one secondary source states it
Who was responsible
the model provider
C one secondary source states it
What went wrong
security breach
C one secondary source states it
primary risk
RK04
D inferred by us from the described behaviour, reason shown

Impact

Severity
major
D inferred by us from the described behaviour, reason shown
Why this severity
Test: unbounded scope stated. Fact: any free account holder can read every project created before the November 2025 cutoff.
D inferred by us from the described behaviour, reason shown

Context

Industry
AI app-building software development platform
C one secondary source states it
Country
Sweden
C one secondary source states it

Notes on gaps

Lovable disputes the breach characterization. The Register source contained no incident content.

LR-2026-0500 · version 1 · published 2026-11-01 after automatic checks; not yet checked field by field by a person · JSON