Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.1amended

Rucio WebUI has a Stored Cross-site Scripting (XSS) Vulnerability in its Custom RSE Attribute

CVE-2026-25736GHSA-fq4f-4738-rqxm

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (rucio-webui 39.3.1, 38.5.4, 35.8.3), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • PyPI rucio-webui

    Affected
    < 35.8.3>= 36.0.0rc1, < 38.5.4>= 39.0.0rc1, < 39.3.1
    Fixed in
    39.3.1, 38.5.4, 35.8.3

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
6.1 · CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:N
EPSS
  • CVE-2026-25736: 0.34% estimated exploitation activity in the next 30 days; percentile 27.32 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary A stored Cross-site Scripting (XSS) vulnerability was identified in the Custom RSE Attribute 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 stored XSS payload can be introduced via a custom RSE attribute value and is later rendered when the RSE is viewed. Create Path: Admin RSE Management RSE NAME Add Attribute Trigger Path: Admin RSE Management RSE NAME Request Response Storing XSS Payload in RSE Attribute <img width="1234" height="844" alt="Storing XSS Payload in RSE Attribute" src="https://github.com/user-attachments/assets/d10f58c2-8cea-43a9-bf7f-f94ef3d1fd81" / XSS Payload triggering when viewing RSE <img width="1248" height="949" alt="XSS Payload triggering when viewing RSE"…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-fq4f-4738-rqxm

  2. Revision 1 · created ·

    Published from osv record GHSA-fq4f-4738-rqxm

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-25736

Advisory: Rucio WebUI has a Stored Cross-site Scripting (XSS) Vulnerability in its Custom RSE Attribute
IDs: CVE-2026-25736, GHSA-fq4f-4738-rqxm
Record: https://patchnext.com/advisories/cve-2026-25736 (revision 2, source checked 26 Oct 2026, 13:36 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: rucio-webui 39.3.1, 38.5.4, 35.8.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI rucio-webui: affected < 35.8.3; >= 36.0.0rc1, < 38.5.4; >= 39.0.0rc1, < 39.3.1; fixed in 39.3.1, 38.5.4, 35.8.3

## Suggested inspection (read-only)
- `python -m pip show rucio-webui`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on rucio-webui.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-fq4f-4738-rqxm (OSV record GHSA-fq4f-4738-rqxm lists affected ranges: PyPI rucio-webui >=0 =36.0.0rc1 =39.0.0rc1 <39.3.1 (fixed))
- Verified: https://github.com/advisories/GHSA-fq4f-4738-rqxm (GitHub-reviewed advisory GHSA-fq4f-4738-rqxm lists affected ranges: PyPI rucio-webui >=0 =36.0.0rc1 =39.0.0rc1 <39.3.1)

Commands are suggestions: review each one before running it.

Loading voting…