Information Disclosure in RustFS (CVE-2026-47136)
Summary
Vulnerability in RustFS (CVE-2026-47136). Risk of unauthorized operations or information disclosure. Exploitable via GET /rustfs/console/license. Mitigation: upgrade to 1.0.0-beta.2 or later.
Original description
The description as published by the source.
RustFS is a distributed object storage system built in Rust. Prior to 1.0.0-beta.2, the RustFS console endpoint GET /rustfs/console/license returns parsed license metadata without requiring authentication. The endpoint is registered on the console listener and returns JSON containing license information such as the license subject and expiration timestamp. Any client that can reach the console listener can query this endpoint without credentials. This vulnerability is fixed in 1.0.0-beta.2.
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-47136 has been found in RustFS.
Attackers can target a specific entry point like GET /rustfs/console/license over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade RustFS to 1.0.0-beta.2 or later.
If unsure, ask your IT team or search "RustFS CVE-2026-47136" on the vendor's site.
CVE-2026-47136 (RustFS) — CWE-200
Attack surface: GET /rustfs/console/license
Patched: 1.0.0-beta.2 — 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.
Information disclosure (CWE-200) exists in RustFS. Attackers reach the vulnerable code path via GET /rustfs/console/license.
Check the vendor advisory for the affected versions of RustFS. Attack surface: GET /rustfs/console/license.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.0.0-beta.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /rustfs/console/license requests with malformed payloads or SQL meta-characters. 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 し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /rustfs/console/license' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /rustfs/console/licenseへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade RustFS to 1.0.0-beta.2ステージング環境で 1.0.0-beta.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against GET /rustfs/console/license on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。