#135Case study4 min
Three Supabase misconfigurations worth checking
Review row access, privileged keys and public storage without confusing intended public access with a leak.
Hackaiz team · updated 21/11/2026

011. Private tables with insufficient access rules
Supabase row-level security, usually shortened to RLS, controls which rows a database role can access. A table holding private notes needs rules that match the people allowed to use it. If RLS is disabled, or a policy permits more than intended, a request may return information that the interface hides. Enabling RLS alone is not a complete review: the policies and grants still need to reflect your application’s intended permissions.
Consider a fictional notes table whose records belong to individual accounts. The useful question is not simply “is RLS enabled?” but “can one account read only the records it is entitled to read?” Hackaiz includes anonymous-query checks and examination of Supabase access rules. Those checks can provide evidence of exposure; they should not be presented as automatic testing of every combination of users, organizations and administrator privileges.
022. A privileged key in browser-delivered code
A Supabase public client key is designed to be used by a client application and is not automatically a leaked secret. A service_role key is different: it carries elevated privileges and must not be shipped in browser code. Renaming the variable or hiding the configuration page does not keep a value secret once it has been included in a downloadable application bundle.
Hackaiz checks for exposed keys and tokens in the browser bundle or connected repository. If a finding concerns a privileged key, review where that value is delivered, remove it from client-side use and have the responsible developer revoke or rotate it through the appropriate provider controls. Rotation is an operational response for your team, not a promise that a proposed code change automatically invalidates the old credential.
033. Storage made public when the files are private
A public storage bucket can be appropriate for product pictures or other intentionally published assets. It is not an appropriate default for identity documents or private attachments. Knowing a long file address is not the same as being authorized to read the file. Write down which categories of files should be public, then examine storage findings against that decision rather than treating all public buckets as identical.
Hackaiz includes checks for public storage and anonymously accessible Supabase resources. An observed public resource is evidence about that resource, not an inventory proving that every file has been examined. When investigating, use synthetic files and avoid pasting private download links into public discussions. Ask your developer to check both the bucket’s visibility and the rules that govern legitimate file access.
04Run a scoped check and review the correction
Begin on “Scan your platform” and select the system you are authorized to examine. If you submit the website or API address, domain ownership proof must be validated first: use DNS TXT _hackaiz, the HTTPS file /.well-known/hackaiz-verification.txt, or the project-AI instruction that creates the verification file. Connecting an authorized GitHub repository adds code evidence; it does not make a repository-only report a complete statement about the live database.
Compare the evidence with the intended data model, then review the findings grouped as Danger, To fix and To watch. Corrections offered through GitHub are draft pull requests for human review and approval, never automatic merges. After an approved fix is deployed, rerun the relevant checks on the affected environment. Analyses and follow-up actions consume credits, while unticked checks are neither executed nor billed. Do not describe an excluded storage check as a clean storage result.
- 1List private tables, privileged credentials and file categories before reviewing the findings.
- 2Identify the exact table, key location or storage resource mentioned in each relevant result.
- 3Have a developer review the proposed change and verify that authorized access still works after deployment.
Frequently asked questions
Take the next step
Was this article helpful?