CVE-2026-25138: Rucio WebUI has Username Enumeration via Login Error Message
Summary The WebUI login endpoint returns distinct error messages depending on whether a supplied username exists, allowing unauthenticated attackers to enumerate valid usernames. Details When submitting invalid credentials to /ui/login, the WebUI responds with different error messages based on the existence of the provided username (identity).
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
The WebUI login endpoint returns distinct error messages depending on whether a supplied username exists, allowing unauthenticated attackers to enumerate valid usernames.
Details
When submitting invalid credentials to /ui/login, the WebUI responds with different error messages based on the existence of the provided username (identity). A non-existent username results in an error indicating that no account is associated with the identity, while an existing username with an incorrect password produces a different authentication-related error.
This behavioral difference allows an attacker to distinguish valid usernames from invalid ones by observing the response content.
Proof of Concept
Bogus Login (Non-existent Username "15251087") Response contains:
Cannot get find any account associated with 15251087 identity.Bogus Login (Existing Username "root", Wrong Password) Response contains:
Cannot get auth token. It is possible that the presented identity root is not mapped to any Rucio account root.The difference in error messages confirms whether a username exists.
Impact
An unauthenticated attacker can enumerate valid usernames, which may be leveraged for targeted password guessing, credential stuffing, or social engineering attacks.
Remediation / Mitigation
Return a generic authentication failure message for all login errors, regardless of whether the username exists. Avoid disclosing account or identity existence through error responses. Consider implementing rate limiting or additional login throttling to further reduce abuse.
Reources:
- OWASP Authentication Cheat Sheet - Authentication and Error Messages: https://cheatsheetseries.owasp.org/cheatsheets/Authentication_Cheat_Sheet.html#authentication-and-error-messages
Credited to d-woosley.
References
- https://github.com/rucio/rucio/security/advisories/GHSA-38wq-6q2w-hcf9
- https://cheatsheetseries.owasp.org/cheatsheets/Authentication_Cheat_Sheet.html#authentication-and-error-messages
- https://github.com/rucio/rucio/releases/tag/35.8.3
- https://github.com/rucio/rucio/releases/tag/38.5.4
- https://github.com/rucio/rucio/releases/tag/39.3.1
- https://nvd.nist.gov/vuln/detail/CVE-2026-25138
- https://github.com/advisories/GHSA-38wq-6q2w-hcf9
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 entriesCVE-2026-25136
Rucio WebUI has a Reflected Cross-site Scripting Vulnerability
high8.1Feb 25, 2026CVE-2026-25733
Rucio WebUI Vulnerable to Stored Cross-site Scripting (XSS) through Custom Rule Function
high7.3Feb 25, 2026CVE-2026-25734
Rucio WebUI has Stored Cross-site Scripting (XSS) in RSE Metadata
medium6.1Feb 25, 2026CVE-2026-25735
Rucio WebUI has a Stored Cross-site Scripting (XSS) vulnerability its Identity Name
medium6.1Feb 25, 2026CVE-2026-25736
Rucio WebUI has a Stored Cross-site Scripting (XSS) Vulnerability in its Custom RSE Attribute
medium6.1Feb 25, 2026
