{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-31945 exists.","fix":"No fix has been published for CVE-2026-31945 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-31945 is a high-severity server-side request forgery vulnerability in Librechat Librechat, published on 27 Mar 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-31945 and fix it if it is affected.\n\nWhat it is: CVE-2026-31945 is a high-severity server-side request forgery vulnerability in Librechat Librechat, published on 27 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-31945 exists.\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-31945/ (Markdown: https://insights.sbomify.com/CVE-2026-31945/index.md)","id":"CVE-2026-31945","markdown":"https://insights.sbomify.com/CVE-2026-31945/index.md","name":"CVE-2026-31945","record":{"aliases":["GHSA-f92m-jpv7-55p2"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"LibreChat web application","requires_auth":"low_privilege","summary":"Attackers can bypass hostname validation via DNS resolution to access internal resources in LibreChat agent actions or MCP features.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"librechat","vendor":"librechat"}],"cvss":{"score":7.7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"LibreChat is a ChatGPT clone with additional features. Versions 0.8.2-rc2 through 0.8.2 are vulnerable to a server-side request forgery (SSRF) attack when using agent actions or MCP. Although a previous SSRF vulnerability (https://github.com/danny-avila/LibreChat/security/advisories/GHSA-rgjq-4q58-m3q8) was reported and patched, the fix only introduced hostname validation. It does not verify whether DNS resolution results in a private IP address. As a result, an attacker can still bypass the protection and gain access to internal resources, such as an internal RAG API or cloud instance metadata endpoints. Version 0.8.3-rc1 contains a patch.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"LibreChat Server-Side Request Forgery using DNS resolution","id":"CVE-2026-31945","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"librechat:librechat","products":["librechat:librechat"],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"OpenOLAT: Authentication bypass via forged JWT in OIDC implicit flow","id":"CVE-2026-31946"},"packages":[],"prev":{"headline":"LibreChat MCP OAuth callback does not validate browser session — allows token theft via redirect link","id":"CVE-2026-31944"},"products":["LibreChat"],"published":"2026-03-27","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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-30","vendors":["danny-avila"]},"summary":"Attackers can bypass hostname validation via DNS resolution to access internal resources in LibreChat agent actions or MCP features.","url":"https://insights.sbomify.com/CVE-2026-31945/"}