{"answers":{"affected":"2 open source packages ship an affected version, including @langchain/redis.","exploited":"There is no known exploitation of CVE-2026-105799 in the wild and no public exploit code.","fix":"Upgrade @langchain/redis to 1.1.1 or later.","what":"CVE-2026-105799 is a low-severity vulnerability in @langchain langchainjs, published on 6 Oct 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-105799 and fix it if it is affected.\n\nWhat it is: CVE-2026-105799 is a low-severity vulnerability in @langchain langchainjs, published on 6 Oct 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-105799 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @langchain/redis (npm): affected all versions; fixed in 1.1.1\n- @langchain/redis (npm): affected all versions; fixed in 1.1.1\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-105799/ (Markdown: https://insights.sbomify.com/CVE-2026-105799/index.md)","id":"CVE-2026-105799","markdown":"https://insights.sbomify.com/CVE-2026-105799/index.md","name":"CVE-2026-105799","record":{"aliases":["CLEANSTART-2026-TL42570","GHSA-5x6v-p487-7qh2"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"LangChain Redis integration","requires_auth":"low_privilege","summary":"Attackers can inject RediSearch syntax to bypass access controls and read unauthorized indexed documents in LangChain Redis integrations.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":2.3,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-943","name":"Improper Neutralization of Special Elements in Data Query Logic"}],"description":"LangChain is a framework for building LLM-powered applications. Prior to 1.1.1, @langchain/redis does not escape attacker-controlled values in structured RediSearch TAG filters and structured RediSearch TEXT filters, allowing injected RediSearch syntax to alter or broaden the generated search query. When an application uses an attacker-influenceable filter as a tenant or document-access boundary, the modified query can expose indexed documents outside the attacker's intended scope. This issue is fixed in version 1.1.1.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"LangChain: RediSearch Filter Injection via Unescaped Tag/Text Values","id":"CVE-2026-105799","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"other","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"i18next-http-backend incomplete URL validation permits SSRF","id":"CVE-2026-105800"},"packages":[{"ecosystem":"npm","fixed":["1.1.1"],"introduced":["0"],"last_affected":[],"package":"@langchain/redis","purl":null,"source":"GHSA-5x6v-p487-7qh2"},{"ecosystem":"npm","fixed":["1.1.1"],"introduced":["0"],"last_affected":[],"package":"@langchain/redis","purl":"pkg:npm/%40langchain/redis","source":"GHSA-5x6v-p487-7qh2"}],"prev":{"headline":"SimpleChat: Stored XSS via group document filename in inline onclick handler","id":"CVE-2026-105798"},"products":["langchainjs","redis"],"published":"2026-10-06","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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-10-06","vendors":["@langchain","langchain-ai"]},"summary":"Attackers can inject RediSearch syntax to bypass access controls and read unauthorized indexed documents in LangChain Redis integrations.","url":"https://insights.sbomify.com/CVE-2026-105799/"}