Back to Feed
BreachesSep 28, 2026

Misconfigured Supabase apps expose data in over 16,000 databases

Over 16,000 Supabase databases exposed PII, passwords, and auth tokens due to misconfigurations.

Researchers discovered that more than 16,000 Supabase databases were misconfigured, leading to the exposure of sensitive data including PII, passwords, and authentication tokens. While a small portion may include credit card data, the primary cause is attributed to poor application security configurations, such as missing row-level security policies, with a notable trend of AI-assisted development contributing to these issues.

AI summary of the linked source. Not reviewed by an editor. How this works

Vendor Watch

Run UpGuard?

Get an email when a new story names UpGuard, usually within the hour.

Free. Your list stays private and never appears in a subject line. One click stops it. How Vendor Watch worksPrivacy

The lesson from this incident

Full lesson

Over 16,000 Supabase databases were left exposed due to missing or improperly configured row-level security (RLS) policies, allowing unauthorized access to sensitive data including PII, passwords, and authentication tokens. The root cause lies in developers — particularly those leveraging AI-assisted development tools — deploying databases without fully understanding or implementing proper security configurations. This highlights a growing risk where the speed of AI-generated code outpaces security best practices, resulting in production systems that are functionally complete but dangerously exposed. The exposure of authentication tokens and credentials compounds the risk, as attackers can pivot from data theft to full account takeover. This incident underscores that cloud-native platforms still require deliberate security hardening regardless of how the application was built.

What helps against this

How we list vendors

Entities

Supabase (product)PostgreSQL (technology)artificial intelligence (technology)UpGuard (vendor)