CVE-2026-55873 is a medium-severity (CVSS 4.3) CWE-863 vulnerability in github.com/seaweedfs/seaweedfs. O3 Security confirms whether CVE-2026-55873 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
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.
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 CVE-2026-55873 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 CVE-2026-55873 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 CVE-2026-55873. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-55873 in your dependencies?
O3 detects CVE-2026-55873 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.