Vulnerability in RustFS (CVE-2026-55189)
Summary
Vulnerability in RustFS (CVE-2026-55189). Confidential information can be exposed externally. Mitigation: upgrade to 1.0.0-beta.9 or later.
Original description
The description as published by the source.
RustFS is a distributed object storage system built in Rust. From 1.0.0-alpha.1 until 1.0.0-beta.9, when the FTP frontend is enabled, the FTP read and probe handlers dispatch directly to the storage backend without ever calling the IAM authorization function that the FTP write/list handlers (and the entire HTTP S3 path) use. As a result, any user who can authenticate to the FTP listener — including a user whose IAM policy contains an explicit Deny on s3:GetObject — can read (RETR) and stat (SIZE/MDTM) any object in any bucket, and probe any bucket (CWD), completely regardless of their IAM policy. This vulnerability is fixed in 1.0.0-beta.9.
Source: NIST National Vulnerability Database NVD
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-55189 has been found in RustFS.
Confidential information can be exposed externally. CVSS score: 7.7/10.
What to do: upgrade RustFS to 1.0.0-beta.9 or later.
If unsure, ask your IT team or search "RustFS CVE-2026-55189" on the vendor's site.
CVE-2026-55189 (RustFS) — CWE-862 / CVSS v3 7.7
Attack vector: remote (network-reachable) / no user interaction
Patched: 1.0.0-beta.9 — apply immediately
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.
A vulnerability (CWE-862) exists in RustFS.
Check the vendor advisory for the affected versions of RustFS.
Severity: High (CVSS 7.7/10). Confidential information can be exposed externally.
Update to 1.0.0-beta.9.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'RustFS' . 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 'RustFS' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
RustFSを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade RustFS to 1.0.0-beta.9ステージング環境で 1.0.0-beta.9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web github.com