# CVE-2026-55873: SeaweedFS: Improper authorization in the S3Tables / Iceberg REST management API lets a low-privileged S3 user enumerate administrator-owned table buckets

> Low-privileged S3 users can enumerate administrator-owned table buckets due to improper authorization in the S3Tables management API.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Jul 2026
- **Updated:** 8 Jul 2026
- **Also known as:** BIT-seaweedfs-2026-55873, GHSA-hgpf-8634-g44c, GO-2026-6329, MINI-3fc5-7g54-5fc3, MINI-hw99-52g3-56qp

## What is CVE-2026-55873?

CVE-2026-55873 is a medium-severity missing authorization vulnerability in seaweedfs, published on 8 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SeaweedFS is a distributed storage system. In versions 4.08 through 4.33, requests signed with SigV4 service s3tables are routed to the S3Tables management API where authorization collapses account-less S3 identities into the shared admin account and fails open, allowing an authenticated low-privileged S3 user to enumerate administrator-owned table bucket names and ARNs. This issue is fixed in version 4.34.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-55873?

4 open source packages ship an affected version, including github.com/seaweedfs/seaweedfs and seaweedfs.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/seaweedfs/seaweedfs` | Go | From 0.0.0-20260128085517-09bb90e8dc16 | 0.0.0-20260614205536-b13463880c1f |
| `github.com/seaweedfs/seaweedfs` | Go | From 0.0.0-20260128085517-09bb90e8dc16 | 0.0.0-20260614205536-b13463880c1f |
| `github.com/seaweedfs/seaweedfs` | Go | From 0.0.0-20260128085517-09bb90e8dc16 | 0.0.0-20260614205536-b13463880c1f |
| `seaweedfs` | Bitnami | All versions | 4.34.0 |

## How do I fix CVE-2026-55873?

Upgrade github.com/seaweedfs/seaweedfs to 0.0.0-20260614205536-b13463880c1f or later.

## Is CVE-2026-55873 being exploited?

There is no known exploitation of CVE-2026-55873 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-55873 and fix it if it is affected.

What it is: CVE-2026-55873 is a medium-severity missing authorization vulnerability in seaweedfs, published on 8 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-55873 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/seaweedfs/seaweedfs (Go): affected from 0.0.0-20260128085517-09bb90e8dc16; fixed in 0.0.0-20260614205536-b13463880c1f
- github.com/seaweedfs/seaweedfs (Go): affected from 0.0.0-20260128085517-09bb90e8dc16; fixed in 0.0.0-20260614205536-b13463880c1f
- github.com/seaweedfs/seaweedfs (Go): affected from 0.0.0-20260128085517-09bb90e8dc16; fixed in 0.0.0-20260614205536-b13463880c1f
- seaweedfs (Bitnami): affected all versions; fixed in 4.34.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-55873/ (Markdown: https://insights.sbomify.com/CVE-2026-55873/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-55873
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-55873
- OSV: https://osv.dev/vulnerability/CVE-2026-55873

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-55873/
Summaries are generated and may contain mistakes; the official description above is the record.