1min.

1MIN · PRODUCTION ENGINEERING

A Lovable audit separates public access from confirmed exposure

Crissy Field researchers examined archived Lovable projects using Supabase and found examples of personal data accessible without signing in. Their broader scan also counted tables containing email addresses, but that signal alone does not establish a leak: addresses can be public or test data. The report highlights missing database access controls rather than a public browser API key by itself.

Crissy Field

Why it matters

A generated interface can appear finished while its underlying data permissions still allow unintended reads.

More context

Undated report discovery; its archive sample spans December 2025 through September 2026. For an application you own, check logged-out access and whether one account can read another account’s records. Confirm intended table permissions instead of treating every public read as a vulnerability.

Keep in mind

Researcher-reported examples, not independently accessed here. The sample is not representative of all Lovable apps, covers Supabase integrations rather than the native database, and does not establish malicious exploitation.

Original read

More engineering ideas, one minute at a time.

Explore more stories