Authorization Flaw in github.com/seaweedfs/seaweedfs (CVE-2026-55873)
Summary
Vulnerability in github.com/seaweedfs/seaweedfs (CVE-2026-55873). Risk of unauthorized operations or information disclosure. Exploitable via GET /buckets. Mitigation: upgrade to 0.0.0-20260614205536-b13463880c1f or later.
Original description
The description as published by the source.
SeaweedFS: Improper authorization in the S3Tables / Iceberg REST management API lets a low-privileged S3 user enumerate administrator-owned table buckets in github.com/seaweedfs/seaweedfs
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-55873 has been found in github.com/seaweedfs/seaweedfs.
Attackers can target a specific entry point like GET /buckets over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade github.com/seaweedfs/seaweedfs to 0.0.0-20260614205536-b13463880c1f or later.
If unsure, ask your IT team or search "github.com/seaweedfs/seaweedfs CVE-2026-55873" on the vendor's site.
CVE-2026-55873 (github.com/seaweedfs/seaweedfs) — CWE-863 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /buckets / s3tables / admin / Read
Patched: 0.0.0-20260614205536-b13463880c1f — apply immediately
Workaround: No configuration workaround — upgrade to 4.34 or later.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Incorrect authorization (CWE-863) exists in github.com/seaweedfs/seaweedfs. Attackers reach the vulnerable code path via GET /buckets.
Check the vendor advisory for the affected versions of github.com/seaweedfs/seaweedfs. Attack surface: GET /buckets / s3tables / admin / Read.
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.
Update to 0.0.0-20260614205536-b13463880c1f.
Workaround: No configuration workaround — upgrade to 4.34 or later.
Search webserver/proxy logs for unusual GET /buckets requests with malformed payloads or SQL meta-characters. Run grep -r 'github.com/seaweedfs/seaweedfs' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/seaweedfs/seaweedfs' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/seaweedfs/seaweedfsを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /buckets' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /bucketsへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply temporary workaround mitigate
No configuration workaround — upgrade to 4.34 or later.パッチが適用されるまでの応急処置として、No configuration workaround — upgrade to 4.34 or later. を実施。回避策の副作用 (機能低下) を確認した上で。
-
4Apply patch patch
Upgrade github.com/seaweedfs/seaweedfs to 0.0.0-20260614205536-b13463880c1fステージング環境で 0.0.0-20260614205536-b13463880c1f に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
5Post-deployment verification verify
Replay attack against GET /buckets on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- patch github.com
- web github.com
- web github.com