{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-54739 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-54739 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-54739 is a medium-severity vulnerability in LemmyNet lemmy, published on 19 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-54739 and fix it if it is affected.\n\nWhat it is: CVE-2026-54739 is a medium-severity vulnerability in LemmyNet lemmy, published on 19 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-54739 in the wild and no public exploit code.\n\nAffected product: LemmyNet lemmy. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-54739/ (Markdown: https://insights.sbomify.com/CVE-2026-54739/index.md)","id":"CVE-2026-54739","markdown":"https://insights.sbomify.com/CVE-2026-54739/index.md","name":"CVE-2026-54739","record":{"aliases":["GHSA-xgg7-8hvq-8m65"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Fediverse link aggregator","requires_auth":"none","summary":"An unauthenticated attacker can enumerate registered usernames or emails by observing HTTP response code differences on the login endpoint.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-204","name":"Observable Response Discrepancy"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Lemmy: Login Endpoint User Enumeration via HTTP Response Code Differential","id":"CVE-2026-54739","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"Lemmy: Lower-ranked federated moderator can remove higher-ranked moderators","id":"CVE-2026-54740"},"packages":[],"prev":{"headline":"Lemmy: Rate limit bypass via X-Forwarded-For header spoofing in actix-web ConnectionInfo","id":"CVE-2026-54738"},"products":["lemmy"],"published":"2026-08-19","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-21","vendors":["LemmyNet"]},"summary":"An unauthenticated attacker can enumerate registered usernames or emails by observing HTTP response code differences on the login endpoint.","url":"https://insights.sbomify.com/CVE-2026-54739/"}