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

Advisory record · `GHSA-hgpf-8634-g44c`

- **Identifiers:** `GHSA-hgpf-8634-g44c` · `BIT-seaweedfs-2026-55873` · `CVE-2026-55873` · `GO-2026-6329`
- **State:** Confirmed
- **Severity:** CVSS 4.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-863](https://cwe.mitre.org/data/definitions/863.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 28 Aug 2026
- **Updated:** 2 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 28 Aug 2026, 22:16 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/seaweedfs/seaweedfs` (Go): affected `>=0.0.0-20260128085517-09bb90e8dc16, <0.0.0-20260614205536-b13463880c1f`; fixed in `0.0.0-20260614205536-b13463880c1f`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> SeaweedFS S3Tables management API, including the Iceberg REST catalog it backs, is vulnerable in versions from 0.0.0-20260128085517-09bb90e8dc16 before 0.0.0-20260614205536-b13463880c1f. An authenticated S3 user with only ordinary Read permission, and no S3Tables permission, can call management operations and list administrator-owned table bucket names and ARNs. Upgrade to 0.0.0-20260614205536-b13463880c1f or later. No configuration workaround is given.

Written 6 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 4.3 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0034, the 28th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:47 UTC: First seen by agentprime
- 31 Oct 2026, 14:47 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-hgpf-8634-g44c)

## Sources

- [GitHub Advisory Database: GHSA-hgpf-8634-g44c](https://github.com/advisories/GHSA-hgpf-8634-g44c)
- [OSV: GHSA-hgpf-8634-g44c](https://osv.dev/vulnerability/GHSA-hgpf-8634-g44c)
- <https://github.com/seaweedfs/seaweedfs/security/advisories/GHSA-hgpf-8634-g44c>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-55873>
- <https://github.com/seaweedfs/seaweedfs/pull/9961>
- <https://github.com/seaweedfs/seaweedfs/commit/b13463880c1fa62e255c058a9228b63cc95b4b36>
- <https://github.com/seaweedfs/seaweedfs>
- <https://github.com/seaweedfs/seaweedfs/releases/tag/4.34>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-hgpf-8634-g44c>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-hgpf-8634-g44c/>. Everything for agents: <https://agentprime.io/llms.txt>.
