Vulnerability · Published Feb 25, 2026 · Assigned by GitHub_M
CVE-2026-27794LangGraph: BaseCache Deserialization of Untrusted Data may lead to Remote Code Execution
Medium 6.6
In plain English
A medium-severity unsafe deserialization in langgraph-checkpoint from langchain-ai. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.8% (higher than 58% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
LangGraph Checkpoint defines the base interface for LangGraph checkpointers. Prior to version 4.0.0, a Remote Code Execution vulnerability exists in LangGraph's caching layer when applications enable cache backends that inherit from `BaseCache` and opt nodes into caching via `CachePolicy`. Prior to `langgraph-checkpoint` 4.0.0, `BaseCache` defaults to `JsonPlusSerializer(pickle_fallback=True)`. When msgpack serialization fails, cached values can be deserialized via `pickle.loads(...)`. Caching is not enabled by default. Applications are affected only when the application explicitly enables a cache backend (for example by passing `cache=...` to `StateGraph.compile(...)` or otherwise configuring a `BaseCache` implementation), one or more nodes opt into caching via `CachePolicy`, and the attacker can write to the cache backend (for example a network-accessible Redis instance with weak/no auth, shared cache infrastructure reachable by other tenants/services, or a writable SQLite cache file). An attacker must be able to write attacker-controlled bytes into the cache backend such that the LangGraph process later reads and deserializes them. This typically requires write access to a networked cache (for example a network-accessible Redis instance with weak/no auth or shared cache infrastructure reachable by other tenants/services) or write access to local cache storage (for example a writable SQLite cache file via permissive file permissions or a shared writable volume). Because exploitation requires write access to the cache storage layer, this is a post-compromise / post-access escalation vector. LangGraph Checkpoint 4.0.0 patches the issue.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| PyPI | langgraph-checkpoint | 4.0.0 | GHSA-mhr3-j7m5-c7c9 |
| PyPI | langgraph-checkpoint | 4.0.0 | PYSEC-2026-2574 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| langchain-ai | langgraph-checkpoint | < 4.0.0 |
Weakness: CWE-502 · Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H
References
- https://github.com/langchain-ai/langgraph/security/advisories/GHSA-mhr3-j7m5-c7c9 x_refsource_CONFIRM
- https://github.com/langchain-ai/langgraph/pull/6677 x_refsource_MISC
- https://github.com/langchain-ai/langgraph/commit/f91d79d0c86932ded6e3b9f195d5a0bbd5aef99c x_refsource_MISC
- https://github.com/langchain-ai/langgraph/releases/tag/checkpoint%3D%3D4.0.0 x_refsource_MISC