LIVE LOG · entries last verified against sources October 14, 2026 · site updated Oct 14, 2026, 1:42 AM ET

← All incidents

CVE-2025-48757: missing Row Level Security in Lovable-generated apps (170 of 1,645 scanned)

Vulnerability · Lovable + Supabase · CRITICAL

Incident dateNot stated (discovered Mar 20, 2025)
DisclosedMay 29, 2025 (researcher). NVD published May 30, 2025.
Added hereOct 13, 11:49 PM ET
Last verifiedOct 14, 2026

Summary

Researcher Matt Palmer scanned the homepages of 1,645 Lovable projects in March 2025 and found 303 database endpoints across 170 projects (about 10.3%) with RLS settings that let unauthenticated visitors read or write data. Exposed data included emails, phone numbers, payment details and API keys. NVD lists it as CVSS 9.3. Lovable disputes the CVE, saying each customer is responsible for protecting their app's data.

Severity

CRITICAL Unauthenticated read/write on user data in a meaningful share of sampled apps. Scored 9.3 Critical by the CNA.

Timeline

  1. Mar 20, 2025
    Issue discovered.
  2. Mar 21, 2025
    Scan of 1,645 projects completed; Lovable notified.
  3. Mar 24, 2025
    Lovable acknowledges the report.
  4. Apr 24, 2025
    Lovable releases a security scan feature (listed as the patch release in Palmer's timeline).
  5. May 29, 2025
    Public disclosure. NVD publishes CVE-2025-48757 on May 30; Lovable disputes platform responsibility.

How it happened

Lovable apps talk to Supabase directly from the browser with the anon key. That design depends on RLS policies being present and correct on every table. Where policies were missing or were effectively 'true for everyone', changing a request (for example adding ?select=*) returned other users' rows. Lovable later introduced a security scanner. Palmer's view is that it only checks whether an RLS policy exists, not whether it is correct.

How to check your app

Sources

Corrections and updates

  1. Oct 14, 2026
    Clarified that the scan covered project homepages only, as the researcher states.
  2. Oct 14, 2026
    Expanded the timeline from the researcher's disclosure timeline (vendor notified Mar 21, acknowledged Mar 24, security scan released Apr 24, public May 29).
  3. Oct 14, 2026
    Replaced 'a check at publish time that warns when RLS is off' with the researcher's own description: a security scanner that only checks whether an RLS policy exists.
If you would rather have someone look at your app for this kind of problem, LockedVibe runs security scans for vibe-coded apps. Their free Lockdown Pack is a good first step too.