Summary
LangGraph: Namespace labels containing . reach other namespaces in Postgres and SQLite stores
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.
Details
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",))andlist_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.
Impact
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.
The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
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.
Frequently Asked Questions
- What is CVE-2026-115883? CVE-2026-115883 is a medium-severity improper input validation vulnerability in langgraph-checkpoint-postgres (pip), affecting versions < 3.1.3. It is fixed in 3.1.3, 3.1.2. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
- Which packages are affected by CVE-2026-115883?
langgraph-checkpoint-postgres(pip) (versions < 3.1.3)langgraph-checkpoint-sqlite(pip) (versions < 3.1.2)
- Is there a fix for CVE-2026-115883? Yes. CVE-2026-115883 is fixed in 3.1.3, 3.1.2. Upgrade to this version or later.
- Is CVE-2026-115883 exploitable, and should I be worried? Whether CVE-2026-115883 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-115883 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-115883?
- Upgrade
langgraph-checkpoint-postgresto 3.1.3 or later - Upgrade
langgraph-checkpoint-sqliteto 3.1.2 or later
- Upgrade