Supabase Storage let unauthenticated callers overwrite objects
Short answer
On October 14, 2026, Supabase published GHSA-8rrf-w776-x75g. Storage versions 1.80.1 and earlier let an unauthenticated caller create or overwrite objects in public or private buckets by reaching the signed resumable-upload route without a signed-upload token. The request then ran with a privileged database connection, so row-level security did not apply. Version 1.80.2 checks the token from the matched route instead of the raw URL. The advisory does not say the hosted platform was already patched.
Last updated · Sekrd Research
- Advisory: GHSA-8rrf-w776-x75g, published October 14, 2026 by ferhatelmas. Critical. No CVE id is shown on the advisory.
- Affected: supabase/storage (storage-api) versions 1.80.1 and earlier. Patched in 1.80.2.
- Impact: unauthenticated creation or overwrite of objects in public or private buckets, including replacing an object with an empty file. Confidentiality impact on the CVSS vector is none. Integrity and availability are high.
- Cause: the signed-upload token check looked at a raw URL prefix. Encoded paths and absolute-form targets could miss that prefix and still hit a route that uses a privileged database role.
- Credit: Elias Hasas (@zer0d4y5). Weaknesses: CWE-172 and CWE-288.
What happened
Supabase Storage’s signed resumable uploads are supposed to be authorized by a token, not by the caller’s JWT. The October 14 advisory says that check could be skipped. An unauthenticated request that reached the route was then executed on a database connection that bypasses row-level security. Anyone who knew a bucket name and an object name could create an object or overwrite one. A zero-byte upload could replace an existing object with an empty file.
The advisory rates the issue critical. The CVSS 3.1 vector it prints is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H. That vector says the bug changes or destroys data. It does not, on its own, describe reading private objects. A later Storage advisory, GHSA-fgvp-cqg6-q8h2, is the one that includes private reads.
Timeline
- October 14, 2026. GHSA-8rrf-w776-x75g published. Affected range: versions at or below 1.80.1. Fix: 1.80.2.
- The fix, in the advisory’s words: signed uploads are identified from the matched route’s request context instead of the raw URL. A valid token for that bucket and object is required before the upload is processed, including before the bucket lookup that sets size limits. The token also controls the upload owner and whether overwriting is allowed.
Why the token check missed
Signed resumable uploads use a privileged database connection because the signed token, not the caller’s JWT, is the authorization. In the affected versions the code decided whether to require that token by asking if the raw request URL started with a fixed path prefix. The router and that check did not agree on every request target. Percent-encoded paths and absolute-form request targets could land on the signed-upload route without matching the prefix. The request continued without an x-signature token being validated.
The remaining permission check then ran as the privileged database user. Row-level security policies did not apply to that connection. This is the same family of mistake as a path filter that looks at the string the client sent instead of the path the router actually dispatched. CWE-172 is the encoding mismatch. CWE-288 is the alternate path that skips authentication.
The advisory tells operators to upgrade to the latest version and says the fix is available from 1.80.2. It does not say Supabase Cloud had already rolled the patch out. If you use hosted Supabase, do not treat silence in this advisory as a statement that your project was updated on October 14. If you run storage-api yourself, the version pin is yours to change.
How to check if your app is exposed
- If you self-host Storage, read the image tag or the package version. Anything at or below 1.80.1 is in the affected range. Move to 1.80.2 or later and restart the service. The advisory does not list a configuration workaround.
- If you use Supabase Cloud, check Supabase’s status or dashboard release notes for the storage component. This GitHub advisory does not document the hosted rollout.
- Know which buckets hold user files. A public bucket of logos is a different asset from a private bucket of identity documents, but the advisory says both public and private buckets were writable through the bypass. Overwrite is the impact even when the bucket was private.
- After you patch, spot-check objects that should not have changed during the window you were exposed: size, checksum, and updated time. A zero-byte object that used to have content is the shape the advisory names.
- Keep doing the ordinary Storage checks. A public bucket still serves files by URL with no policy. Private buckets still need policies on
storage.objects. That checklist is separate from this bug and is written up in the RLS checklist.
How Sekrd helps
Sekrd does not send the request that skips this token check, and it does not claim to have tested your storage-api version. A deep scan reports a public S3 or GCS bucket, already linked from the page, whose listing names a credential or database object. It also reports Supabase tables that return rows to the publishable key. Those are different bugs, with different rules: supabase-rls-bypass and the bucket probe described in the November scanner update.
For a Lovable or Bolt app on Supabase, the standing checks are still the ones that show up every week: secret key in the bundle, USING (true), and a private table that answers anonymously. Start with the Supabase RLS checker or a free scan of the deployed URL. The upload bypass is fixed by upgrading Storage, not by a policy tweak.
Related reading
Frequently asked questions
Which Supabase Storage versions are affected by GHSA-8rrf-w776-x75g?
Versions 1.80.1 and earlier. The patched version named in the advisory is 1.80.2.
Does the bug let an attacker read private files?
The advisory describes creating and overwriting objects, including emptying an existing object. Its CVSS vector sets confidentiality to none and integrity and availability to high. It does not describe a read of private objects.
Is hosted Supabase already patched for this?
The October 14 advisory does not say that. It tells operators to upgrade to 1.80.2 or later. A different Storage advisory, published November 6, does say the hosted platform is already patched for that later bug.
Do I need a signed URL to be affected?
The vulnerable route is the one normally used for signed resumable uploads. The bug is that a crafted request could reach it without a valid x-signature token. The advisory says an attacker needed to know the bucket and object name.
Will Row Level Security stop the overwrite?
Not on the affected versions. The advisory says the upload continued on a privileged database connection, so RLS policies did not prevent it. The 1.80.2 fix requires the signed token before that work happens.
Sources
Don't ship until you're sekrd
Run a free scan to find the vulnerabilities your AI missed.
Scan Your App Free