Vulnerability in rucio-webui (CVE-2026-25138)
Summary
Vulnerability in rucio-webui (CVE-2026-25138). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 39.3.1 or later.
Original description
The description as published by the source.
Rucio is a software framework that provides functionality to organize, manage, and access large volumes of scientific data using customizable policies. Prior to versions 35.8.3, 38.5.4, and 39.3.1, the WebUI login endpoint returns distinct error messages depending on whether a supplied username exists, allowing unauthenticated attackers to enumerate valid usernames. Versions 35.8.3, 38.5.4, and 39.3.1 fix the issue.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
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-25138 has been found in rucio-webui.
Risk of unauthorized operations or information disclosure.
What to do: upgrade rucio-webui to 39.3.1 or later.
If unsure, ask your IT team or search "rucio-webui CVE-2026-25138" on the vendor's site.
CVE-2026-25138 (rucio-webui) — CWE-204
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 39.3.1 — 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-204) exists in rucio-webui.
Check the vendor advisory for the affected versions of rucio-webui.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 39.3.1.
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 'rucio-webui' . 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 'rucio-webui' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
rucio-webuiを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade rucio-webui to 39.3.1ステージング環境で 39.3.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web cheatsheetseries.owasp.org
- web github.com
- web github.com
- web github.com