Vulnerability in @langchain/redis (CVE-2026-105799)
Summary
Vulnerability in @langchain/redis (CVE-2026-105799). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.1.1 or later.
Original description
The description as published by the source.
Summary
@langchain/redis did not properly escape values used to construct structured RediSearch TAG and TEXT filters. An application that passes attacker-controlled values into these filters could allow the attacker to alter the resulting search query.
Affected versions
@langchain/redis versions through 1.1.0 are affected.
Impact
An attacker who can control values passed to the affected structured TAG or TEXT filters can inject RediSearch syntax and alter or broaden the resulting search query. In applications that use an attacker-influenceable filter as a tenant or document-access boundary, this may expose indexed documents outside the attacker's intended scope.
Remediation
Upgrade to @langchain/redis 1.1.1 or later.
The fix escapes RediSearch special characters, validates field names and structured filter types, and applies these protections across fluent filter builders and custom-schema query construction.
Credits
Thanks to @thesanjok and @shovanchakraborty for reporting this issue.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-105799 has been found in @langchain/redis.
Risk of unauthorized operations or information disclosure.
What to do: upgrade @langchain/redis to 1.1.1 or later.
If unsure, ask your IT team or search "@langchain/redis CVE-2026-105799" on the vendor's site.
CVE-2026-105799 (@langchain/redis) — CWE-943
Patched: 1.1.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-943) exists in @langchain/redis.
Check the vendor advisory for the affected versions of @langchain/redis.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.1.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@langchain/redis' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@langchain/redis' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@langchain/redisを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @langchain/redis to 1.1.1ステージング環境で 1.1.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com