GHSA-hgpf-8634-g44c is a medium-severity (CVSS 4.3) CWE-863 vulnerability in github.com/seaweedfs/seaweedfs. O3 Security confirms whether GHSA-hgpf-8634-g44c is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
SeaweedFS: Improper authorization in the S3Tables / Iceberg REST management API lets a low-privileged S3 user enumerate administrator-owned table buckets
Real-World Exposure
github.com/seaweedfs/seaweedfsReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Summary
SeaweedFS routes requests signed with SigV4 service s3tables to the S3Tables
management API. Authorization on that path collapsed account-less S3 identities
into the shared admin account and failed open, so a user holding only ordinary
S3 Read credentials — and no S3Tables-specific permission — could invoke
S3Tables management operations such as GET /buckets and enumerate
administrator-owned table bucket inventory (names and ARNs). The same handler
backs the Iceberg REST catalog, which was affected by the same flaw.
Impact
An authenticated low-privileged S3 user can cross the boundary between ordinary S3 object access and S3Tables management. Confirmed impact is disclosure of administrator-owned table bucket inventory (bucket names and ARNs); in shared or multi-tenant deployments this can reveal tenant naming and operational structure.
Affected versions
SeaweedFS >= 4.08, < 4.34 (the S3Tables management API was introduced in 4.08).
Patched versions
Fixed in 4.34 (#9961). Administrator status is now decided by the
ACTION_ADMIN capability rather than by a collapsed admin account id, S3Tables
authorization no longer defaults to allow, and the tautological ListTableBuckets
gate was removed. Related hardening of the same root cause landed in #9962,
#9963, and #9971.
Workaround
No configuration workaround — upgrade to 4.34 or later.
Credit
Reported by TA-MU-TA.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/seaweedfs/seaweedfs | ≥ 0.0.0-20260128085517-09bb90e8dc16&&< 0.0.0-20260614205536-b13463880c1f | 0.0.0-20260614205536-b13463880c1f |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/seaweedfs/seaweedfs. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/seaweedfs/seaweedfs to 0.0.0-20260614205536-b13463880c1f or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hgpf-8634-g44c is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-hgpf-8634-g44c is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-hgpf-8634-g44c. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-hgpf-8634-g44c in your dependencies?
O3 detects GHSA-hgpf-8634-g44c across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.