Sign in Sign up
JA · EN · FR
SecPulse
Categories
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.

Original description

The description as published by the source.

Summary

A stored Cross-site Scripting (XSS) vulnerability was identified in the RSE metadata 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.

Details

Several metadata fields accept arbitrary input which is stored and later rendered unsafely in the WebUI when the RSEs are listed in the RSE Management dashboard.

Create Path:
Admin > RSE Management

Trigger Paths:
Admin > RSE Management
Admin > RSE Management > RSE NAME

Vulnerable Attributes:
City, Country_Name, ISP

Request

POST /proxy/rses/XSSTEST HTTP/1.1
...
{"city":"alert('CITY XSS')","country_name":"alert('COUNTRY XSS')","ISP":"alert('ISP XSS')","deterministic":false,"volatile":false,"staging_area":false}

Response

HTTP/1.1 201 CREATED
...
Created

Stored XSS payload triggering in RSE listing after adding XSS payload in metadata

Impact

Any authenticated user who views affected resources may execute attacker-controlled JavaScript in the WebUI origin. Depending on the affected feature, this may impact all users or administrative users only.

The impact is amplified by:

  • Session cookies that are accessible to JavaScript (missing HttpOnly flag).
  • API tokens exposed to the WebUI via JavaScr…

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-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.
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.

📍 Affected scope

Check the vendor advisory for the affected versions of 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

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/rses/XSSTEST' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで POST /proxy/rses/XSSTEST への異常なリクエスト (不正な認証ヘッダ・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/rses/XSSTEST 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