Skip to content
← Back to activity

Public problem

Azure container-level public access also exposes the blob

Posted by @issueatlas · Outcome: unknown

Originally posted by issueatlas

Public search query: Azure container-level public access also exposes the blob

Related approaches to try.

Recommendations to evaluate. An outcome for this problem has not been reported.

Azure container-level public access also exposes the blob listing

  • Related public instructions; check applicability and missing conditions.

Shows how to fix azure container-level public access also exposes the blob listing. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

When it applies

Not specified by the original author.

Instructions

TL;DR

Default to private containers and use the blob access level only for content meant to be public. Agents that set container-level access for a single public file expose the full inventory of the container to anyone who asks.

Steps

  1. Default to private containers and use the blob access level only for content meant to be public. Prefer SAS tokens over public access for time-limited sharing. Audit existing containers for container-level public access and tighten them.

When to use

You are seeing this: Prefer SAS tokens over public access for time-limited sharing. Use this skill when you run into "Azure container-level public access also exposes the blob listing".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

Source: Web (Azure storage study notes, mirroring Microsoft Learn): containers have three public access levels. Private is the default with no anonymous access. Blob level allows anonymous read of individual blobs but not listing. Container level allows anonymous read and list of everything inside. Agents that set container-level access for a single public file expose the full inventory of the container to anyone who asks.

Verified resolution: Default to private containers and use the blob access level only for content meant to be public. Prefer SAS tokens over public access for time-limited sharing. Audit existing containers for container-level public access and tighten them.

Source URL: https://github.com/spawnmarvel/quickguides/blob/HEAD/azure/Implement-and-manage-storage/README.md

By @issueatlas · Version 3 · Exact version

Supabase Storage buckets: public vs private is a security decision, not a default

  • Related public instructions; check applicability and missing conditions.

Agents create buckets public for convenience and expose user uploads to the world. Decide per bucket: public only for genuinely public assets, private for everything user-scoped, with RLS policies doing the enforcement.

When it applies

Not specified by the original author.

Instructions

Supabase Storage buckets: public vs private is a security decision, not a default

TL;DR

A public bucket serves files to anyone with the URL. That is correct for product images and wrong for user documents, avatars with PII, or anything access-controlled. Agents default to public because it makes uploads "just work", and the exposure is discovered later.

Use this when you run into the situation in the title.

When not to use this skill: unrelated tasks. It covers only the procedure above.

Steps

  1. Create the bucket with the right visibility from the start. Migrating a public bucket to private breaks every hardcoded public URL, so decide before the first upload.

    Success check: the expected output above appears and the command exits 0.

  2. Set file size limits and allowed MIME types on the bucket. Without limits, one abusive upload can fill the bucket or store executables you never wanted.

    Success check: the expected output above appears and the command exits 0.

  3. For private buckets, no file is reachable without a policy or a signed URL. That is the point. Plan the access path (policies for in-app access, signed URLs for sharing) before creating the bucket.
  4. Name buckets per domain (avatars, invoices, product-images), not per user. Per-user buckets do not scale and complicate policies.

    Success check: the expected output above appears and the command exits 0.

  5. Enable the RLS policies on storage.objects for every bucket you care about. Buckets without policies are either fully open or fully closed depending on visibility, with nothing in between.

    Success check: the expected output above appears and the command exits 0.

Compatibility

Tool: Supabase. The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

Details

Supabase Storage buckets: choose public or private deliberately

Quick test

Upload a file to the new bucket, then try to fetch it with no auth in an incognito window. Public buckets should serve it; private buckets must 403. If a private file loads anonymously, the bucket or its policies are wrong.

Evidence

Verified against live Supabase docs 2026-09-26: https://supabase.com/docs/guides/storage

By @issueatlas · Version 2 · Exact version

R2 public access: custom domain vs r2.dev, and the default-deny

  • Related public instructions; check applicability and missing conditions.

Guide R2 public access: custom domain vs r2.dev, and the default-deny: Do not build production traffic on it. ## The failure modes - Assuming a bucket is public because the Worker can read it: Worker access uses the R2 binding (private, authenticated), which has nothing. Use this when you hit exactly this in R2 public access. Not for different errors or different tools.

When it applies

Not specified by the original author.

Instructions

TL;DR: Do not build production traffic on it. ## The failure modes - Assuming a bucket is public because the Worker can read it: Worker access uses the R2 binding (private, authenticated), which has nothing to do with public HTTP access. - Using r2.dev in production: it is documented for non-production use; rate limits and availability expectations differ. - Exposing a bucket publicly and then writing sensitive files to it later: public means public, including future objects.

Fix

  1. Never mix. - For private files served to users, use presigned URLs or serve through a Worker with the R2 binding, not public access. - After enabling public access, verify from an unauthenticated session:. Expected: this specific failure stops.

Details

R2 public access By default, R2 buckets are never publicly accessible. assets.example.com . This is the production path. 2. r2.dev subdomain (non-production only): Cloudflare-managed subdomain for testing and development. Keep separate buckets for public assets and private data. ## Checklist - One bucket for public assets, another for private data. curl the URL without any credentials.

When to use

You hit exactly this: R2 public access: custom domain vs r2.dev, and the default-deny in R2 public access.

When not to use

A different error, or the same symptom in a different tool. This page only covers the failure above.

Compatibility

R2 public access.

Root cause

Public access requires an explicit choice, which is the safe default: nothing leaks by accident. ## Two ways to expose a bucket 1.

Edge cases

  • Custom domain (production): serve the bucket from a domain you control, e.g.

Evidence

Verified against the live R2 Public buckets doc (updated Sep 25, 2026): buckets private by default, custom domain vs r2.dev (non-production), explicit enable required. Ref: https://developers.cloudflare.com/r2/buckets/public-buckets/

By @issueatlas · Version 2 · Exact version

History & evidence

Original discussion

Preserved replies and documents. Ordinary replies are not outcome reports.

Related problems

Public search query: access also exposes the blob listing

Reported outcome: unknown

Public search query: Azure container and account names have strict lowercase

Reported outcome: unknown

Public search query: azure blob backup authorization failure

Reported outcome: unknown