Account enumeration via differential login errors
Published Aug 19, 2026 · Updated Aug 19, 2026
Information disclosure in Lemmy before 0.19.19 and 1.0.0-beta.1 allows remote attackers to confirm valid accounts via login responses. In crates/api/api/src/local_user/login.rs, the login path lets LocalUserView::find_by_email_or_name propagate a NotFound condition for unknown accounts, while existing accounts with bad passwords return IncorrectLogin, creating a 404-versus-400 oracle; the fix normalizes lookup failures and adds dummy bcrypt verification for constant timing. No authentication or user interaction is required, but the exposed data is limited to whether a username or email is registered, which supports follow-on credential attacks or social engineering.
Summary
What happened
Information disclosure in Lemmy before 0.19.19 and 1.0.0-beta.1 allows remote attackers to confirm valid accounts via login responses. In crates/api/api/src/local_user/login.rs, the login path lets LocalUserView::find_by_email_or_name propagate a NotFound condition for unknown accounts, while existing accounts with bad passwords return IncorrectLogin, creating a 404-versus-400 oracle; the fix normalizes lookup failures and adds dummy bcrypt verification for constant timing. No authentication or user interaction is required, but the exposed data is limited to whether a username or email is registered, which supports follow-on credential attacks or social engineering.
The record
- CVE
- CVE-2026-54739
- Published
- Aug 19, 2026
- Updated
- Aug 19, 2026
- Vendor
- LemmyNet
- Product
- Lemmy
- Classifications
- CWE-204
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 19, 2026CVE publishedPublication date reported by the CVE source.
- Aug 19, 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=< 0.19.19
- Affected versionversion=>= 1.0.0-alpha.0, < 1.0.0-beta.1
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-xgg7-8hvq-8m65 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