criticalexposurepublic probe
Table readable with the anon key
ANON_TABLE_READABLEThis table returned rows to an unauthenticated request carrying only the public anon key. Anything visible here is visible to the internet.
What the finding looks like
criticalTable "invoices" returned 1,247 rows to the public anon key
How to fix it
The public probe knows the table is readable but not why, because it cannot see your policies. Enable and force RLS, then connect the project for policy suggestions generated from the real column names.
Related guides
What people search for
supabase anon key full table accesssupabase data leaklovable app leaking supabase data
Check your own project
This rule runs on the free probe. A URL is the only input.
Run the free audit