← Back
CVE-2026-27794
Unsafe Deserialization in langgraph-checkpoint (CVE-2026-27794)
Summary
vulnerability in langgraph-checkpoint (CVE-2026-27794). Successful exploitation can lead to full system takeover. Exploitable via ``BaseCache``. Mitigation: upgrade to `4.0.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-27794** has been found in langgraph-checkpoint.
Attackers can target a specific entry point like ``BaseCache`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: ?/10.
What to do: upgrade langgraph-checkpoint to **4.0.0** or later.
If unsure, ask your IT team or search "langgraph-checkpoint CVE-2026-27794" on the vendor's site.
CVE-2026-27794 (langgraph-checkpoint) — CWE-502 /
Attack vector: remote (network-reachable) / no user interaction
Attack surface: `BaseCache` / `CachePolicy` / `JsonPlusSerializer` / `InMemoryCache`
Patched: `4.0.0` — 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
**unsafe deserialization** (CWE-502) exists in langgraph-checkpoint. Attackers reach the vulnerable code path via ``BaseCache`` without authentication.
📍 Affected scope
langgraph-checkpoint — . Attack surface: `BaseCache` / `CachePolicy` / `JsonPlusSerializer` / `InMemoryCache`.
🔥 Severity
Severity: ?. Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **4.0.0**.
🛡️ 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 'langgraph-checkpoint' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'langgraph-checkpoint' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `langgraph-checkpoint` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade langgraph-checkpoint to 4.0.0ステージング環境で 4.0.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
langgraph-checkpoint
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.0.0"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-27794
- advisory https://github.com/advisories/GHSA-mhr3-j7m5-c7c9
- package https://github.com/langchain-ai/langgraph
- package https://pypi.org/project/langgraph-checkpoint
- web https://github.com/langchain-ai/langgraph/security/advisories/GHSA-mhr3-j7m5-c7c9
- web https://github.com/langchain-ai/langgraph/pull/6677
- web https://github.com/langchain-ai/langgraph/commit/f91d79d0c86932ded6e3b9f195d5a0bbd5aef99c
- web https://github.com/langchain-ai/langgraph/releases/tag/checkpoint%3D%3D4.0.0