{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-54037 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-54037 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-54037 is a medium-severity denial of service vulnerability in Librechat Librechat, published on 25 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-54037 and fix it if it is affected.\n\nWhat it is: CVE-2026-54037 is a medium-severity denial of service vulnerability in Librechat Librechat, published on 25 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-54037 in the wild and no public exploit code.\n\nAffected product: Librechat Librechat. 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-54037/ (Markdown: https://insights.sbomify.com/CVE-2026-54037/index.md)","id":"CVE-2026-54037","markdown":"https://insights.sbomify.com/CVE-2026-54037/index.md","name":"CVE-2026-54037","record":{"aliases":["GHSA-g445-9wq6-jf3v"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"LibreChat web app","requires_auth":"low_privilege","summary":"Authenticated users can exhaust server resources by bypassing rate limits on the conversation duplication endpoint, causing denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"librechat","vendor":"librechat"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"description":"LibreChat is an enhanced ChatGPT clone that supports multiple AI providers. Prior to 0.8.4-rc1, the fix for CVE-2025-7105 added forkIpLimiter and forkUserLimiter rate limiters to POST /api/convos/fork to prevent rapid-fire conversation duplication. However, the POST /api/convos/duplicate endpoint — which is in the same file and performs the exact same expensive database operations — was not given any rate limiter. An authenticated user can bypass the CVE-2025-7105 fix by using /duplicate instead of /fork to exhaust server resources. This vulnerability is fixed in 0.8.4-rc1.","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":"LibreChat: Incomplete Fix for CVE-2025-7105 — /api/convos/duplicate Lacks Rate Limiting Applied to /api/convos/fork","id":"CVE-2026-54037","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"librechat:librechat","products":["librechat:librechat"],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"LibreChat: 2FA Backup Code Regeneration Without OTP Verification Allows 2FA Bypass","id":"CVE-2026-54040"},"packages":[],"prev":{"headline":"LibreChat: 2FA Re-enrollment Allows Full Account 2FA Takeover Without OTP Verification","id":"CVE-2026-54036"},"products":["LibreChat"],"published":"2026-06-25","related":[{"cvss_score":9.6,"headline":"LibreChat Exfiltrates Server Secrets via MCP Server URL Injection","id":"CVE-2026-32625","kev_date_added":null,"published":"2026-06-02"},{"cvss_score":9.4,"headline":"Improper Access Control in danny-avila/librechat","id":"CVE-2024-11167","kev_date_added":null,"published":"2025-03-20"},{"cvss_score":9.1,"headline":"LibreChat MCP Stdio Remote Command Execution","id":"CVE-2026-22252","kev_date_added":null,"published":"2026-01-12"},{"cvss_score":9.1,"headline":"LibreChat is vulnerable to Server-Side Request Forgery due to missing restrictions","id":"CVE-2025-69222","kev_date_added":null,"published":"2026-01-07"},{"cvss_score":9.1,"headline":"Path traversal in n/a","id":"CVE-2024-41704","kev_date_added":null,"published":"2024-07-22"},{"cvss_score":8.8,"headline":"Path Traversal in danny-avila/librechat","id":"CVE-2024-11170","kev_date_added":null,"published":"2025-03-20"},{"cvss_score":8.6,"headline":"LibreChat JSON Injection in Chat POST Allows Remote Resource Inclusion and PXSS via Image Upload","id":"CVE-2025-66450","kev_date_added":null,"published":"2025-12-11"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-25","vendors":["danny-avila"]},"summary":"Authenticated users can exhaust server resources by bypassing rate limits on the conversation duplication endpoint, causing denial of service.","url":"https://insights.sbomify.com/CVE-2026-54037/"}