Authentication Bypass Using an Alternate Path or Channel and Authentication Bypass by Primary Weakness in rucio-webui

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Impact rucio-webui installations of the 1.26 release line potentially leak the contents of cookies to other sessions within a wsgi container. Impact is that Rucio authentication tokens are leaked to other users accessing the webui within a close timeframe, thus allowing users to access the webui with the leaked authentication token. Privileges are therefore also escalated. Rucio server / daemons are not affected by this issue, it is isolated to the webui. Patches This issue is fixed in the 1.26.7 release of the rucio-webui. Workarounds Installation of the 1.25.7 webui release. The 1.25 and previous webui release lines are not affected by this issue. References https://github.com/rucio/rucio/issues/4928

Published by the source

22 Oct 2021, 16:21 UTC

Last modified by the source

13 Feb 2025, 05:31 UTC

Source last checked

26 Oct 2026, 13:11 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-v988-828w-xvf2

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-v988-828w-xvf2

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

# Patch Next advisory brief: GHSA-v988-828w-xvf2

Advisory: Authentication Bypass Using an Alternate Path or Channel and Authentication Bypass by Primary Weakness in rucio-webui
IDs: GHSA-v988-828w-xvf2
Record: https://patchnext.com/advisories/ghsa-v988-828w-xvf2 (revision 2, source checked 26 Oct 2026, 13:11 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: rucio-webui 1.26.7. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI rucio-webui: affected >= 1.26.0, < 1.26.7; fixed in 1.26.7

## 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-v988-828w-xvf2 (OSV record GHSA-v988-828w-xvf2 lists affected ranges: PyPI rucio-webui >=1.26.0 <1.26.7 (fixed))
- Verified: https://github.com/advisories/GHSA-v988-828w-xvf2 (GitHub-reviewed advisory GHSA-v988-828w-xvf2 lists affected ranges: PyPI rucio-webui >=1.26.0 <1.26.7)

Commands are suggestions: review each one before running it.