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.
CVE-2026-54739
This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 64% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.9
- EG Score
- 6.9(medium)
- EG Risk
- 46(Track)EG Risk 46/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity69% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 36%
- KEV
- Not listed
Published
August 19, 2026
Last Modified
August 21, 2026
Advisory Details (8)
Auto-updated Aug 19, 20262026-06-09 - Lemmy Release v0.19.19
https://join-lemmy.org/news/2026-06-09_-_Lemmy_Release_v0.19.191.0.0-beta.1
Patch available: LemmyNet/lemmy 1.0.0-beta.1 (pre-release)
https://github.com/LemmyNet/lemmy/releases/tag/1.0.0-beta.10.19.19
Patch available: LemmyNet/lemmy 0.19.19
https://github.com/LemmyNet/lemmy/releases/tag/0.19.19commit 59e968a5ac36 (LemmyNet/lemmy)
Patch available: LemmyNet/lemmy 0.19.19 (contains commit 59e968a5ac36)
https://github.com/LemmyNet/lemmy/commit/59e968a5ac36d36d08a59028e2dbb92641536964commit 4d235a1b668b (LemmyNet/lemmy)
Patch available: LemmyNet/lemmy 1.0.0-beta.1 (contains commit 4d235a1b668b)
https://github.com/LemmyNet/lemmy/commit/4d235a1b668b7dda6b73dbbc9ca289bb40acfa83[0.19] Prevent user enumeration via login endpoint
Patch available: LemmyNet/lemmy 0.19.19 (PR #6535 merged 2026-05-27)
https://github.com/LemmyNet/lemmy/pull/6535Prevent user enumeration via login endpoint
Patch available: LemmyNet/lemmy 1.0.0-beta.1 (PR #6531 merged 2026-06-01)
https://github.com/LemmyNet/lemmy/pull/6531Login Endpoint User Enumeration via HTTP Response Code Differential · Advisory · LemmyNet/lemmy · GitHub
https://github.com/LemmyNet/lemmy/security/advisories/GHSA-xgg7-8hvq-8m65Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 14× in last 7d / 14× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-25 15:53 UTCEG score recompute
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 17:32 UTCEG score recompute
- 2026-08-23 19:10 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 20:48 UTCEG score recompute
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 22:26 UTCEG score recompute
- 2026-08-21 22:00 UTCEG score recompute
- 2026-08-21 18:05 UTCEG score recompute
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-19 21:20 UTCEG score recompute
- 2026-08-19 20:28 UTCEG score recompute
- 2026-08-19 20:27 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-54739?
When was CVE-2026-54739 disclosed?
Is CVE-2026-54739 actively exploited?
What is the CVSS score of CVE-2026-54739?
How do I remediate CVE-2026-54739?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-54739
Is Your Infrastructure Affected by CVE-2026-54739?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.