{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-54738 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-54738 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-54738 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-54738 and fix it if it is affected.\n\nWhat it is: CVE-2026-54738 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-54738 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-54738/ (Markdown: https://insights.sbomify.com/CVE-2026-54738/index.md)","id":"CVE-2026-54738","markdown":"https://insights.sbomify.com/CVE-2026-54738/index.md","name":"CVE-2026-54738","record":{"aliases":["GHSA-2hrg-7x4g-9vpg"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Fediverse link aggregator","requires_auth":"none","summary":"Attackers can bypass rate limits in Lemmy by spoofing the X-Forwarded-For header, enabling spam, brute-force attacks, and excessive account creation.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-799","name":"Improper Control of Interaction Frequency"}],"description":"Lemmy is a link aggregator and forum for the fediverse. Prior to 0.19.19 and 1.0.0-beta.1, actix-web ConnectionInfo::realip_remote_addr reads the first value of X-Forwarded-For as the client address used by raw_ip_key in crates/utils/src/rate_limit/mod.rs. Lemmy's bundled docker/nginx.conf uses $proxy_add_x_forwarded_for instead of $remote_addr, which appends the real client address to an X-Forwarded-For value supplied by the client. An unauthenticated attacker can therefore place a different spoofed address first on each request and receive a new rate-limit bucket, bypassing limits on POST /api/v4/account/auth/register, POST /api/v4/account/auth/login, POST /api/v4/post, POST /api/v4/comment, GET /api/v4/search, POST /api/v4/image, and POST /api/v4/account/import_settings. This permits excessive account creation, brute-force attempts, spam, scraping, uploads, and repeated imports. 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: Rate limit bypass via X-Forwarded-For header spoofing in actix-web ConnectionInfo","id":"CVE-2026-54738","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"Lemmy: Login Endpoint User Enumeration via HTTP Response Code Differential","id":"CVE-2026-54739"},"packages":[],"prev":{"headline":"@phun-ky/defaults-deep Has a Prototype Pollution issue via Unsafe Recursive Property Merging","id":"CVE-2026-54737"},"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":"Attackers can bypass rate limits in Lemmy by spoofing the X-Forwarded-For header, enabling spam, brute-force attacks, and excessive account creation.","url":"https://insights.sbomify.com/CVE-2026-54738/"}