An honest security analysis of Supabase for developers considering it for their projects.
Supabase is secure by design, but YOUR configuration determines app security. The anon key is meant to be public - security comes from Row Level Security (RLS) policies you must enable and configure.
Supabase is a secure platform when configured correctly. The critical step is enabling and properly configuring Row Level Security. Most 'Supabase breaches' are actually developer misconfigurations, not platform vulnerabilities.
Understanding Supabase security in the context of broader industry trends and research.
of Lovable applications (170 out of 1,645) had exposed user data in the CVE-2025-48757 incident
Source: CVE-2025-48757 security advisory
of data breaches involve databases with misconfigured access controls
Source: Verizon Data Breach Investigations Report
average cost of a data breach in 2023
Source: IBM Cost of a Data Breach Report 2023
“Row Level Security is not optional for production applications. Without RLS, your anon key grants full public access to your database.”
“Service keys should never be used in the browser or exposed to customers. They bypass all Row Level Security policies.”
Don't guess - scan your app and know for certain. VAS checks for all the common security issues in Supabase applications.