Quick answers
- Is CVE-2026-105799 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-105799 being exploited in the wild.
- How severe is CVE-2026-105799?
- Medium severity, with a CVSS score of 4, published 6 October 2026.
- Which products and versions are affected?
- LangChain @Langchain/Redis before 1.1.1; @langchain/redis (npm) <= 1.1.0, SEMVER:introduced=0,fixed=1.1.1.
- Is there a fix for CVE-2026-105799?
- Yes. @langchain/redis (npm): upgrade to 1.1.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-105799 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-105799?
- Check whether you run LangChain @Langchain/Redis or @langchain/redis (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- @langchain/redis (npm): upgrade to 1.1.1 or later
npm install @langchain/redis@1.1.1
Technical details
The @langchain/redis library did not escape attacker-controlled values in RediSearch TAG and TEXT filter construction, permitting injection of RediSearch syntax to alter or broaden search queries. The vulnerability affects both fluent filter classes and legacy custom-schema query building paths. An attacker who controls filter values (such as tenant identifiers or document access boundaries) can craft queries that bypass access restrictions and retrieve indexed documents outside their intended scope.
Affected products
- LangChain @langchain/redis before 1.1.1
Identifiers
- CVE-2026-105799
- GHSA-5x6v-p487-7qh2
Timeline
- 2026-10-06: disclosed
- 2026-04-14: patched: Fix applied in commit 880e396 before public disclosure