Vulnerability in rucio-webui (CVE-2026-25733)
Summary
Vulnerability in rucio-webui (CVE-2026-25733). Confidential information can be exposed externally. Exploitable via POST /proxy/rules/. 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. Versions prior to 35.8.3, 38.5.4, and 39.3.1 have a stored Cross-Site Scripting (XSS) vulnerability in the Custom Rules function of the WebUI where attacker-controlled input is persisted by the backend and later rendered in the WebUI without proper output encoding. This allows arbitrary JavaScript execution in the context of the WebUI for users who view affected pages, potentially enabling session token theft or unauthorized actions. 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-25733 has been found in rucio-webui.
Attackers can target a specific entry point like POST /proxy/rules/ over the network to misuse the product.
Confidential information can be exposed externally.
What to do: upgrade rucio-webui to 39.3.1 or later.
If unsure, ask your IT team or search "rucio-webui CVE-2026-25733" on the vendor's site.
CVE-2026-25733 (rucio-webui) — CWE-1004
Attack vector: remote (network-reachable)
Attack surface: POST /proxy/rules/ / comment / 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.
A vulnerability (CWE-1004) exists in rucio-webui. Attackers reach the vulnerable code path via POST /proxy/rules/.
Check the vendor advisory for the affected versions of rucio-webui. Attack surface: POST /proxy/rules/ / comment / token.
Severity: ?. Confidential information can be exposed externally.
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 POST /proxy/rules/ 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
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 し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /proxy/rules/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /proxy/rules/への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade rucio-webui to 39.3.1ステージング環境で 39.3.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /proxy/rules/ on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
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