Username enumeration via login timing discrepancy
Published Mar 13, 2026 · Updated Mar 13, 2026
Observable timing discrepancy in Cleanuparr 2.7.0 through 2.8.0 allows remote attackers to enumerate valid usernames via login requests. The /api/auth/login path conditionally short-circuits before its BCrypt-based VerifyPassword call, so some failures skip the dominant hashing cost while others incur it. No credentials or user interaction are required; repeated samples disclose username validity and can alter failed-attempt and lockout state.
Summary
What happened
Observable timing discrepancy in Cleanuparr 2.7.0 through 2.8.0 allows remote attackers to enumerate valid usernames via login requests. The /api/auth/login path conditionally short-circuits before its BCrypt-based VerifyPassword call, so some failures skip the dominant hashing cost while others incur it. No credentials or user interaction are required; repeated samples disclose username validity and can alter failed-attempt and lockout state.
The record
- CVE
- CVE-2026-32702
- Published
- Mar 13, 2026
- Updated
- Mar 13, 2026
- Vendor
- Cleanuparr
- Product
- Cleanuparr
- Classifications
- CWE-208
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 13, 2026CVE publishedPublication date reported by the CVE source.
- Mar 13, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 2.7.0, <= 2.8.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA timing-enumeration proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo