Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-48121 medium CVSS 6.7

Vulnerability in @langchain/langgraph-checkpoint-mongodb (CVE-2026-48121)

Summary

Vulnerability in @langchain/langgraph-checkpoint-mongodb (CVE-2026-48121). Confidential information can be exposed externally. Exploitable via MongoDBSaver. Mitigation: upgrade to 1.3.1 or later.

Original description

The description as published by the source.

Summary

A NoSQL injection vulnerability existed in MongoDBSaver where checkpoint identifier fields from config.configurable were used in MongoDB queries without strict type enforcement. In vulnerable versions, attacker-controlled object payloads (for example MongoDB operators like $gt and $ne) could be interpreted as query operators instead of literal identifier values.

This could bypass intended thread scoping and return checkpoints from other tenants.

Attack surface

The vulnerable path was in MongoDBSaver.getTuple(), where thread_id, checkpoint_ns, and checkpoint_id were used in MongoDB find() queries. The same unvalidated values were then reused to fetch pending writes.

Applications were exposed when untrusted input was forwarded into config.configurable (for example, directly from request bodies or query parameters) without string coercion or schema validation.

Who is affected?

Applications are vulnerable if they:

  • Use @langchain/langgraph-checkpoint-mongodb with multi-tenant or user-isolated thread models.
  • Accept user-controlled values for thread_id, checkpoint_ns, or checkpoint_id.
  • Pass those values into app.invoke(), app.stream(), or direct saver methods without validation.

Applications are generally not vulnerable if they:

  • Use server-issued identifiers only.
  • Source thread_id from trusted URL params that remain strings.
  • Enforce schema validation that rejects non-string identifier fields.

Impact

An att…

Source: GitHub Security Advisories (Global) 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-48121 has been found in @langchain/langgraph-checkpoint-mongodb.
Attackers can target a specific entry point like MongoDBSaver over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.7/10.
What to do: upgrade @langchain/langgraph-checkpoint-mongodb to 1.3.1 or later.
If unsure, ask your IT team or search "@langchain/langgraph-checkpoint-mongodb CVE-2026-48121" on the vendor's site.

CVE-2026-48121 (@langchain/langgraph-checkpoint-mongodb) — CWE-943 / CVSS v3 6.7
Attack vector: adjacent-network
Attack surface: MongoDBSaver / config.configurable / thread_id / checkpoint_ns
Patched: 1.3.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.

❓ What is the problem

A vulnerability (CWE-943) exists in @langchain/langgraph-checkpoint-mongodb. Attackers reach the vulnerable code path via MongoDBSaver.

📍 Affected scope

Check the vendor advisory for the affected versions of @langchain/langgraph-checkpoint-mongodb. Attack surface: MongoDBSaver / config.configurable / thread_id / checkpoint_ns.

🔥 Severity

Severity: Medium (CVSS 6.7/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 1.3.1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@langchain/langgraph-checkpoint-mongodb' . 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

  1. 1
    Identify exposure identify 
    grep -r '@langchain/langgraph-checkpoint-mongodb' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で @langchain/langgraph-checkpoint-mongodb を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade @langchain/langgraph-checkpoint-mongodb to 1.3.1

    ステージング環境で 1.3.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm @langchain/langgraph-checkpoint-mongodb
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.3.1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details