{"answers":{"affected":"2 open source packages ship an affected version, including @langchain/mongodb.","exploited":"There is no known exploitation of CVE-2026-106119 in the wild and no public exploit code.","fix":"Upgrade @langchain/mongodb to 1.3.1 or later.","what":"CVE-2026-106119 is a medium-severity SQL injection 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-106119 and fix it if it is affected.\n\nWhat it is: CVE-2026-106119 is a medium-severity SQL injection 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-106119 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @langchain/mongodb (npm): affected all versions; fixed in 1.3.1\n- @langchain/mongodb (npm): affected all versions; fixed in 1.3.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-106119/ (Markdown: https://insights.sbomify.com/CVE-2026-106119/index.md)","id":"CVE-2026-106119","markdown":"https://insights.sbomify.com/CVE-2026-106119/index.md","name":"CVE-2026-106119","record":{"aliases":["GHSA-m6rx-h84q-8r95"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"LangChain MongoDB integration","requires_auth":"low_privilege","summary":"Attackers can inject MongoDB queries via session IDs to read, modify, or delete other users' chat histories in shared collections.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:L/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.3.1, MongoDBChatMessageHistory does not enforce the documented string type for an untrusted structured session identifier at runtime, allowing the identifier to be interpreted as a MongoDB query condition rather than as a literal value when multiple users' histories are stored in a shared MongoDB collection. An attacker able to invoke chat-history operations can read, modify, or delete another user's stored conversation. Applications using authenticated, server-controlled string identifiers are not affected. This issue is fixed in version 1.3.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: MongoDBChatMessageHistory query injection can allow cross-session access","id":"CVE-2026-106119","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"sql_injection","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"LiquidJS: ownPropertyOnly bypass for inherited array indices in first/last/join/reverse/slice/compact, `.first`/`.last`, negative index, and for-loop iteration","id":"CVE-2026-106120"},"packages":[{"ecosystem":"npm","fixed":["1.3.1"],"introduced":["0"],"last_affected":[],"package":"@langchain/mongodb","purl":null,"source":"GHSA-m6rx-h84q-8r95"},{"ecosystem":"npm","fixed":["1.3.1"],"introduced":["0"],"last_affected":[],"package":"@langchain/mongodb","purl":"pkg:npm/%40langchain/mongodb","source":"GHSA-m6rx-h84q-8r95"}],"prev":{"headline":"ImageSharp: Tiled fax TIFF: tile buffer sized by TileWidth but fax decompressor writes scanlines of ImageWidth — heap OOB write","id":"CVE-2026-106118"},"products":["langchainjs","mongodb"],"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 MongoDB queries via session IDs to read, modify, or delete other users' chat histories in shared collections.","url":"https://insights.sbomify.com/CVE-2026-106119/"}