← Back
CVE-2026-25734
Vulnerability in rucio-webui (CVE-2026-25734)
Summary
vulnerability in rucio-webui (CVE-2026-25734). Confidential information can be exposed externally. Exploitable via `POST /proxy/rses/XSSTEST`. Mitigation: upgrade to `39.3.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-25734** has been found in rucio-webui.
Attackers can target a specific entry point like `POST /proxy/rses/XSSTEST` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: upgrade rucio-webui to **39.3.1** or later.
If unsure, ask your IT team or search "rucio-webui CVE-2026-25734" on the vendor's site.
CVE-2026-25734 (rucio-webui) — CWE-1004 /
Attack vector: remote (network-reachable)
Attack surface: POST /proxy/rses/XSSTEST / `token`
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.
❓ What is the problem
**A vulnerability** (CWE-1004) exists in rucio-webui. Attackers reach the vulnerable code path via `POST /proxy/rses/XSSTEST` without authentication.
📍 Affected scope
rucio-webui — . Attack surface: POST /proxy/rses/XSSTEST / `token`.
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **39.3.1**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual `POST /proxy/rses/XSSTEST` requests with malformed payloads or SQL meta-characters. Run `grep -r 'rucio-webui' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'POST /proxy/rses/XSSTEST' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `POST /proxy/rses/XSSTEST` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
6Apply patch patch
Upgrade rucio-webui to 39.3.1ステージング環境で 39.3.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Replay attack against POST /proxy/rses/XSSTEST on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
rucio-webui
[{"type":"ECOSYSTEM","events":[{"introduced":"39.0.0rc1"},{"fixed":"39.3.1"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-25734
- advisory https://github.com/advisories/GHSA-h9fp-p2p9-873q
- package https://github.com/rucio/rucio
- package https://pypi.org/project/rucio-webui
- web https://github.com/rucio/rucio/security/advisories/GHSA-h9fp-p2p9-873q
- web https://cheatsheetseries.owasp.org/cheatsheets/Cross_Site_Scripting_Prevention_Cheat_Sheet.html
- web https://github.com/rucio/rucio/releases/tag/35.8.3
- web https://github.com/rucio/rucio/releases/tag/38.5.4
- web https://github.com/rucio/rucio/releases/tag/39.3.1