Lemmy: Login Endpoint User Enumeration via HTTP Response Code Differential
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 6.9epss 0.4%
exploitation probability
0.4%top 63% of all CVEs
observed exploitation
nono source reports it
Lemmy is a link aggregator and forum for the fediverse. Prior to 0.19.19 and 1.0.0-beta.1, Lemmy's login endpoint in crates/api/api/src/local_user/login.rs returns different errors depending on whether the username_or_email value exists. LocalUserView::find_by_email_or_name propagates a NotFound response for an unknown account, while an existing account with a wrong password returns LemmyErrorType::IncorrectLogin. This observable response discrepancy, including HTTP 404 for a nonexistent account and HTTP 400 for an incorrect password on an existing account, allows an unauthenticated attacker to confirm registered usernames or email addresses and use the results for targeted credential attacks or social engineering. This issue is fixed in versions 0.19.19 and 1.0.0-beta.1.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
Affected products
LemmyNet · lemmyReferences
https://github.com/LemmyNet/lemmy/commit/4d235a1b668b7dda6b73dbbc9ca289bb40acfa83https://github.com/LemmyNet/lemmy/commit/59e968a5ac36d36d08a59028e2dbb92641536964https://github.com/LemmyNet/lemmy/pull/6531https://github.com/LemmyNet/lemmy/pull/6535https://github.com/LemmyNet/lemmy/releases/tag/0.19.19https://github.com/LemmyNet/lemmy/releases/tag/1.0.0-beta.1https://github.com/LemmyNet/lemmy/security/advisories/GHSA-xgg7-8hvq-8m65https://join-lemmy.org/news/2026-06-09_-_Lemmy_Release_v0.19.19