Supabase "permission denied" after Oct 30: what it means for AI-built apps
If your business runs on an app built with Lovable, Bolt, Cursor or a similar AI tool, there’s a good chance its data lives in Supabase. On Friday, October 30, 2026, Supabase changes one of its defaults. Nothing breaks that day. But the next time someone adds a feature, they may see a “permission denied” error, and the fastest way to make that error go away can expose your data.
Here’s what’s changing, why it matters to a business owner, and what to ask whoever maintains your app.
What Supabase is changing
Until now, every new table created in a Supabase project’s public schema was automatically reachable from the app through Supabase’s Data API. That was convenient, and it’s one reason AI tools could add features so quickly.
From October 30, new tables on existing projects are not reachable from the app until someone explicitly grants access. Supabase announced the change in April and sent a final reminder email to project owners on October 23.
Two things stay the same:
- Your existing tables keep their current access. Today’s app keeps working.
- Row-level security works exactly as before. (Row-level security is the setting that decides which rows each user is allowed to see.)
Supabase’s own notice calls out AI coding tools that create tables and expect them to work right away as directly affected.
Where the risk comes in
Picture a normal week. Someone on your team asks the AI tool to “add a page for tracking equipment.” The tool creates a new table. The page loads, but the data doesn’t, and the error says permission was denied.
The quick fix is one line that grants access to the table. The risky version grants it to anon, the role used by anyone who has your app’s public key. That key ships inside every copy of your app’s web pages, so it isn’t a secret. If that table has no row-level security turned on, every row in it becomes readable by anyone who knows where to look.
An AI tool trying to “make the error go away” can reach for exactly that fix. So can a busy person. A November 2026 scan found thousands of Lovable-built sites with tables open in just this way; see is my Lovable app leaking data?
Is my Lovable app secure after this change?
Your app isn’t less secure on October 30 than it was on October 29. The change actually makes new tables safer by default. The risk is in how the next “permission denied” gets fixed. A safe fix and an unsafe fix look almost the same in a code review, and they produce the same result on screen: the page works.
The safe pattern
Every new table should get three things, in the same change:
- A grant only to the roles that need it. For most business apps, that means signed-in users (
authenticated), notanon. - Row-level security turned on.
- An access policy that says which rows each user can see or change.
For whoever maintains your app, it looks like this (the table and column names are examples):
alter table public.equipment enable row level security;
grant select, insert, update, delete on public.equipment to authenticated;
create policy "Staff see their company's equipment"
on public.equipment for select to authenticated
using (company_id = (select company_id from public.profiles where id = auth.uid()));
If your team builds with an AI tool, add a standing rule to its instructions or project knowledge, for example:
Whenever you create a table, enable row-level security, grant access only to
authenticatedunless told otherwise, and add an access policy in the same migration. Never grant toanonwithout asking first.
What to ask this week
You don’t need to read code to keep this under control. Ask whoever maintains your app:
- Do new tables get grants, row-level security and an access policy in the same change?
- Is “grant to anon” ever used? It should be rare, deliberate and documented.
- When did someone last open Supabase’s Security Advisor? It’s built into the Supabase dashboard and flags tables without row-level security, among other issues.
If nobody can answer those questions with confidence, that’s useful to know before the next feature request, not after. And if your app’s keys are stored on a hosting platform that has reported a breach, start with how to rotate API keys after a hosting platform breach.
Sources
- Supabase changelog: Breaking change: tables not exposed to Data and GraphQL API automatically
Fix Forward Labs helps US businesses keep apps built with AI tools safe and running. Not sure how your app is set up? Our free Forward Scan walks through its 3 biggest risks in a 20-minute video.