Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-25136

Vulnerability in rucio-webui (CVE-2026-25136)

Summary

Vulnerability in rucio-webui (CVE-2026-25136). Confidential information can be exposed externally. Exploitable via POST /proxy/accounts/pentest/attr/XSS. Mitigation: upgrade to 39.3.1 or later.

Original description

The description as published by the source.

Summary

A reflected Cross-site Scripting vulnerability was located in the rendering of the ExceptionMessage of the WebUI 500 error which could allow attackers to steal login session tokens of users who navigate to a specially crafted URL.

Details

The WebUI error message renders ExceptionMessage (which can contain user-controlled input) as unencoded HTML. Server code that produces the message is in common.py - specifically error_headers -> _error_response -> generate_http_error_flask, which places ExceptionMessage into both response headers and the JSON body. The WebUI client then injects that text into the DOM using unsafe methods (examples in lib/rucio/web/ui/static/*.js such as rule.js, request_rule.js, list_rules.js) with jQuery.html(...) or equivalent, enabling reflected XSS when an attacker-controlled value is included in an error message (e.g. account, attribute, scope).

PoC

  1. Reflected XSS via account parameter (browse or load URL in WebUI context):
https://127.0.0.1:8443/ui/account_rse_usage?account=%3Cimg%20src=x%20onerror=alert(document.cookie)%3E

Server response (excerpt):

HTTP/1.1 500 INTERNAL SERVER ERROR
ExceptionClass: AccountNotFound
ExceptionMessage: Account  does not exist
Content-Type: application/octet-stream

{"ExceptionClass":"AccountNotFound","ExceptionMessage":"Account  does not exist"}

XSS payload triggering (Displaying session token) when browsing to crafted URL

When the WebUI inserts `E…

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-25136 has been found in rucio-webui.
Attackers can target a specific entry point like POST /proxy/accounts/pentest/attr/XSS 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-25136" on the vendor's site.

CVE-2026-25136 (rucio-webui) — CWE-1004
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: POST /proxy/accounts/pentest/attr/XSS / ExceptionMessage / common.py / rule.js
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/accounts/pentest/attr/XSS without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of rucio-webui. Attack surface: POST /proxy/accounts/pentest/attr/XSS / ExceptionMessage / common.py / rule.js.

🔥 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/accounts/pentest/attr/XSS 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

  1. 1
    Identify exposure identify 
    grep -r 'rucio-webui' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で rucio-webui を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect 
    grep 'POST /proxy/accounts/pentest/attr/XSS' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで POST /proxy/accounts/pentest/attr/XSS への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch 
    Upgrade rucio-webui to 39.3.1

    ステージング環境で 39.3.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify 
    Replay attack against POST /proxy/accounts/pentest/attr/XSS on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

PyPI rucio-webui
[{"type":"ECOSYSTEM","events":[{"introduced":"39.0.0rc1"},{"fixed":"39.3.1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details