Supabase public buckets bypass signed URLs, exposing private files to anyone
A technical advisory warns that Supabase Storage buckets marked as public allow anyone to access stored files directly via a stable URL, completely bypassing signed URL authentication. This poses a serious risk for developers building private B2B workflows — such as storing generated images in Next.js apps — who mistakenly assume signed URLs alone protect their content. The core issue lies in Supabase's public flag: when set to true, no authentication check is performed before serving objects. Developers are advised to set the bucket's public flag to false, apply row-level security policies, and serve files exclusively through time-limited signed URLs generated server-side. An optional recommendation is to offload CPU-heavy image processing to background workers while keeping all outputs in the now-secured private bucket.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)
Log in to join the discussion and vote.
Log in