Generated stack · Supabase
Supabase
Postgres backend used by Lovable, Bolt and most AI builders.
8Advisories
7critical
1high
0medium
2026-10-10Latest
Timeline · advisories per quarter
12025 Q2
12025 Q3
12026 Q1
12026 Q2
32026 Q3
12026 Q4
Named in sources
Reported for Supabase
01. Supabase RLS policies that check login but not ownershipA policy like using (auth.uid() is not null) has RLS on and mentions the user, so it passes Lovable’s scan. But it lets any logged-in user read every row, and on most apps anyone can sign up. Supabase 
Lovable 
Bolt +4 more 2026-10-10 02. UpGuard: 16,326 Supabase databases had readable tablesUpGuard checked about 300,000 websites that use Supabase and found 16,326 databases with tables anyone could read. Over half showed signs of personal data, and a smaller share held passwords or auth tokens. Supabase 
Claude Code 
Codex CLI +4 more 2026-09-25 03. Supabase tables readable by anyone with no loginA scan of 30,998 live vibe-coded apps found 57% of the Supabase-backed apps it could check served table rows to requests with no login. Lovable Bolt 
v0 +4 more 2026-08 04. Supabase service_role / secret key shipped to the browserThe service_role (or new sb_secret_) key bypasses every RLS policy. If it is in your JavaScript bundle, your whole database is public. Lovable Bolt v0 +4 more 2026-08 05. Moltbook left its Supabase database open to read and writeWiz found that Moltbook, a social network for AI agents whose founder said he vibe-coded it, shipped a Supabase key in its JavaScript with no Row Level Security behind it. Anyone could read and write the database, including 1.5 million agent API tokens and 35,000 email addresses. Supabase 2026-02-02 06. CVE-2025-48757: Lovable apps shipped with missing or weak Supabase RLSLovable-generated apps talked to Supabase directly from the browser, but many tables had no (or wrong) Row Level Security policies, so anyone with the public anon key could read or write data. Lovable Supabase 2025-05 07. Supabase MCP: a support ticket gets the agent to dump private tablesGeneral Analysis showed indirect prompt injection in support-ticket data making an MCP-connected assistant query private tables with Supabase’s privileged service role. 
MCP SDKs & servers Supabase 
Cursor +1 more 2025-07-08
Supabase Lovable Bolt +4 more 2026-10-10 02. UpGuard: 16,326 Supabase databases had readable tablesUpGuard checked about 300,000 websites that use Supabase and found 16,326 databases with tables anyone could read. Over half showed signs of personal data, and a smaller share held passwords or auth tokens. Supabase Claude Code Codex CLI +4 more 2026-09-25 03. Supabase tables readable by anyone with no loginA scan of 30,998 live vibe-coded apps found 57% of the Supabase-backed apps it could check served table rows to requests with no login. Lovable Bolt v0 +4 more 2026-08 04. Supabase service_role / secret key shipped to the browserThe service_role (or new sb_secret_) key bypasses every RLS policy. If it is in your JavaScript bundle, your whole database is public. Lovable Bolt v0 +4 more 2026-08 05. Moltbook left its Supabase database open to read and writeWiz found that Moltbook, a social network for AI agents whose founder said he vibe-coded it, shipped a Supabase key in its JavaScript with no Row Level Security behind it. Anyone could read and write the database, including 1.5 million agent API tokens and 35,000 email addresses. Supabase 2026-02-02 06. CVE-2025-48757: Lovable apps shipped with missing or weak Supabase RLSLovable-generated apps talked to Supabase directly from the browser, but many tables had no (or wrong) Row Level Security policies, so anyone with the public anon key could read or write data. Lovable Supabase 2025-05 07. Supabase MCP: a support ticket gets the agent to dump private tablesGeneral Analysis showed indirect prompt injection in support-ticket data making an MCP-connected assistant query private tables with Supabase’s privileged service role. MCP SDKs & servers Supabase Cursor +1 more 2025-07-08 Same pattern
Stripe