langchain-ai langgraph-checkpoint-postgres Checkpoint Savers input validation

Summaryinfo

A vulnerability has been found in langchain-ai langgraph-checkpoint-postgres and langgraph-checkpoint-sqlite and classified as critical. The impacted element is an unknown function of the component Checkpoint Savers. This manipulation causes input validation. This vulnerability is tracked as CVE-2026-115883. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability has been found in langchain-ai langgraph-checkpoint-postgres and langgraph-checkpoint-sqlite (the affected version unknown) and classified as critical. Affected by this vulnerability is an unknown part of the component Checkpoint Savers. The manipulation with an unknown input leads to a input validation vulnerability. The CWE definition for the vulnerability is CWE-20. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

LangGraph checkpoint savers provide Postgres- and SQLite-backed state persistence for LangGraph workflows and agents. Prior to langgraph-checkpoint-postgres 3.1.3 and langgraph-checkpoint-sqlite 3.1.2, PostgresStore, AsyncPostgresStore, SqliteStore, and AsyncSqliteStore flatten namespace labels with ".".join(namespace), while BaseStore validates labels only for put and aput. Unvalidated dotted labels passed through get, search, delete, list_namespaces, their asynchronous equivalents, or direct batch and abatch operations can resolve to another tenant's stored namespace, allowing cross-namespace reads, overwrites, or deletion. InMemoryStore is not affected because it compares namespace tuples. This issue is fixed in langgraph-checkpoint-postgres 3.1.3 and langgraph-checkpoint-sqlite 3.1.2.

The advisory is shared at github.com. This vulnerability is known as CVE-2026-115883 since 10/23/2026. The exploitation appears to be easy. The attack can be launched remotely. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/23/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Artificial Intelligence Software

Vendor

• langchain-ai

Name

• langgraph-checkpoint-postgres
• langgraph-checkpoint-sqlite

CPE 2.3info

• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion