CVE-2026-106119: langchain-ai langchainjs · Improper Neutralization of Special Elements in Data Query Logic
Affects langchain-ai langchainjsSource CVE Database V5
Not known to be exploited · CVSS 6.0 Medium : upgrade to 1.5.14 when convenient.
Data as of 20 Nov 2026, 17:34 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.5.14, 1.3.1
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 6 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.
What to do
Upgrade langchainjs to 1.5.14; mongodb to 1.3.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| langchain-ailangchainjs | Affected
| Fixed in
|
| @langchainmongodb | Affected
| Fixed in
|
AI-suggested
A fix is available in @langchain/mongodb version 1.3.1 and later. Users should upgrade to this version to ensure session identifiers are validated and treated as literals in MongoDB queries. If immediate upgrade is not possible, applications must reject session identifiers that are not non-empty strings and ensure session identifiers are derived from authenticated, server-controlled values rather than untrusted input. Upgrading remains the recommended remediation.
Description
CVE-2026-106119 is a vulnerability in langchainjs's MongoDBChatMessageHistory component where session identifiers are not properly validated at runtime. This allows specially crafted session identifiers to be interpreted as MongoDB query conditions instead of literal strings. An attacker able to invoke chat-history operations could potentially read, modify, or delete other users' conversation histories if multiple users' data share the same collection. The issue is fixed in @langchain/mongodb version 1.3.1 and later.
References
- github.com/langchain-ai/langchainjs/security/advisories/GHSA-m6rx-h84q-8r95 (opens in a new tab)
- github.com/langchain-ai/langchainjs/pull/11672 (opens in a new tab)
- github.com/langchain-ai/langchainjs/commit/946e3d856ff1f8ce7f7b9374c83f680a6ada79af (opens in a new tab)
- github.com/langchain-ai/langchainjs/releases/tag/@langchain/mongodb@1.3.1 (opens in a new tab)