What is CVE-2026-106119?

CVE-2026-106119 is a medium-severity security vulnerability in @langchain/mongodb (npm), affecting versions <= 1.3.0. It is fixed in 1.3.1.

Which versions of @langchain/mongodb are affected by CVE-2026-106119?

@langchain/mongodb (npm) versions <= 1.3.0 is affected.

Is there a fix for CVE-2026-106119?

Yes. CVE-2026-106119 is fixed in 1.3.1. Upgrade to this version or later.

Is CVE-2026-106119 exploitable, and should I be worried?

Whether CVE-2026-106119 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-106119 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-106119?

Upgrade @langchain/mongodb to 1.3.1 or later.

CVE-2026-106119 in @langchain/mongodb

Q: Which versions of @langchain/mongodb are affected by CVE-2026-106119?

@langchain/mongodb (npm) versions <= 1.3.0 is affected.

Q: Is there a fix for CVE-2026-106119?

Yes. CVE-2026-106119 is fixed in 1.3.1. Upgrade to this version or later.

Q: Is CVE-2026-106119 exploitable, and should I be worried?

Whether CVE-2026-106119 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-106119 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-106119?

Upgrade @langchain/mongodb to 1.3.1 or later.

Summary

LangChain: MongoDBChatMessageHistory query injection can allow cross-session access

Workarounds

If an immediate upgrade is not possible, applications must reject session identifiers that are not non-empty strings. Session identifiers should be derived from an authenticated, server-controlled value and must not be passed directly from an untrusted request field.

Upgrading remains the recommended remediation.

Impact

MongoDBChatMessageHistory did not enforce the documented string type for session identifiers at runtime. In affected applications, a structured session identifier could be interpreted as a MongoDB query condition rather than as a literal identifier.

Applications are affected when they pass untrusted session identifier input to MongoDBChatMessageHistory and store multiple users’ histories in the same collection. An attacker who can invoke chat-history operations may be able to read, modify, or delete another user’s stored conversation.

Applications that derive the session identifier from an authenticated, server-controlled value and enforce its type are not affected by this path.

Affected versions

@langchain/mongodb (<= 1.3.0)

Security releases

@langchain/mongodb → 1.3.1 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

The issue is fixed in @langchain/mongodb version 1.3.1.

Users of affected versions should upgrade to version 1.3.1 or later. The patched version validates session identifiers at runtime and ensures they are compared as literal values in MongoDB queries.

Frequently Asked Questions

What is CVE-2026-106119? CVE-2026-106119 is a medium-severity security vulnerability in @langchain/mongodb (npm), affecting versions <= 1.3.0. It is fixed in 1.3.1.
Which versions of @langchain/mongodb are affected by CVE-2026-106119? @langchain/mongodb (npm) versions <= 1.3.0 is affected.
Is there a fix for CVE-2026-106119? Yes. CVE-2026-106119 is fixed in 1.3.1. Upgrade to this version or later.
Is CVE-2026-106119 exploitable, and should I be worried? Whether CVE-2026-106119 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-106119 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-106119? Upgrade @langchain/mongodb to 1.3.1 or later.