Rucio WebUI has Username Enumeration via Login Error Message
Published Feb 25, 2026 · Updated Oct 23, 2026 · Also known as GHSA-38wq-6q2w-hcf9, PYSEC-2026-3053
Original summary
Normalized public record · Updated Oct 23, 2026
Rucio WebUI has Username Enumeration via Login Error Message
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
The WebUI login endpoint returns distinct error messages depending on whether a supplied username exists, allowing unauthenticated attackers to enumerate valid usernames.
Potential impact
An unauthenticated attacker can enumerate valid usernames, which may be leveraged for targeted password guessing, credential stuffing, or social engineering attacks.
Technical context
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.
Evidence: public source recordsAffected products
| Affected package, product or range | Fix status |
|---|---|
| Consult the referenced vendor advisory for affected versions. | Consult source advisory |
Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.
Remediation
Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.
- Confirm the affected product and reachable code path exist in your environment.
- Apply the vendor-supported patch or mitigation from the primary advisory.
- Rescan the exact deployed revision and retain verification evidence.
Evidence coverage
- SSVC priority
- LOW
- Confidence
- Not available
- Aliases
- GHSA-38wq-6q2w-hcf9, PYSEC-2026-3053
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
- Security advisory ↗
- https://cheatsheetseries.owasp.org/cheatsheets/Authentication_Cheat_Sheet.html#authentication-and-error-messages ↗
- Source repository ↗
- Source repository ↗
- Source repository ↗
Record history
Published Feb 25, 2026 · Last refreshed Oct 23, 2026