Live › vulnerability › CVE-2026-115883
Go to dashboardPostgres and SQLite LangGraph checkpoint stores join namespace labels with dots, so a label containing a dot can address another namespace. A caller who can pass such a label can read, overwrite or delete items belonging to another namespace.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 22:15 UTC, 0h before NVD. All times on this page are UTC.
Applications that use the LangGraph Postgres or SQLite store and build namespaces from untrusted input, such as tenant or user identifiers, are exposed. Systems that use InMemoryStore, or that only use fixed namespaces never derived from user input, are not affected in practice. Stores that do not use these two packages are not covered by the advisory.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| langgraph-checkpoint-postgres | pypi | < 3.1.3 | 3.1.3 |
| langgraph-checkpoint-sqlite | pypi | < 3.1.2 | 3.1.2 |
pip show langgraph-checkpoint-postgres langgraph-checkpoint-sqlite and compare the versions with the fixed onesPostgresStore, AsyncPostgresStore, SqliteStore or AsyncSqliteStore and check whether user input can become a namespace labellanggraph-checkpoint-postgres to 3.1.3 or laterlanggraph-checkpoint-sqlite to 3.1.2 or laterlanggraph-checkpoint 4.3.00.15.5 or 0.16.2 or later (LangSmith Cloud is already patched or patches on next revision)Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
The Postgres and SQLite stores save a namespace as its labels joined with ., so ("tenant", "bob") and ("tenant.bob",) map to the same stored namespace. put rejected labels containing ., but get, search, delete, list_namespaces, their async versions, and ops passed directly to batch/abatch did not. A caller that could pass such a label could read, overwrite or delete items in another namespace.
BaseStore checked namespace labels only in put/aput. The other methods passed the namespace on unchecked, and batch/abatch checked nothing, including the PutOp items inside them. PostgresStore, AsyncPostgresStore, SqliteStore and AsyncSqliteStore turn a namespace into text with ".".join(namespace), so a label containing . resolved to the namespace whose labels it spells out:
get(("tenant.bob",), key), search(("tenant.bob",)) and list_namespaces(prefix=("tenant.bob",)) returned data stored under ("tenant", "bob").delete(("tenant.alice",), key) deleted the item stored under ("tenant", "alice").batch([PutOp(("tenant.bob",), key, value)]) overwrote the item stored under ("tenant", "bob").All releases of langgraph-checkpoint-postgres before 3.1.3 and langgraph-checkpoint-sqlite before 3.1.2 are affected. InMemoryStore compares namespaces as tuples and is not affected.
You may be affected if you use one of these stores, rely on namespaces to keep users or tenants apart, and let untrusted input choose a namespace label that reaches a read, delete or batch call. Such input could read, overwrite or delete another tenant's items. Labels written through put could never contain ., so no stored data becomes unreachable after upgrading.
LangSmith Deployment: the HTTP store API already rejected such labels, but store calls made from graph code reached the same flaw. The Agent Server rejects these labels from versions 0.15.5 and 0.16.2. On LangSmith Cloud, new deployments and revisions already include the fix and existing deployments get it on their next revision; self-hosted deployments should upgrade.
Upgrade to langgraph-checkpoint-postgres 3.1.3 or langgraph-checkpoint-sqlite 3.1.2. Both require langgraph-checkpoint 4.3.0, where get, search, delete and list_namespaces reject labels that are empty, are not strings, or contain . with InvalidNamespaceError, and the Postgres and SQLite stores apply the same check to every op passed to batch/abatch. Stores outside this repository that turn namespaces into delimited text can call langgraph.store.base.validate_op_namespace for each op they run.
This page as .md · .json · in your agent: get_signal("CVE-2026-115883")
GitHub Advisory Database, CC-BY 4.0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.