GHSA-6hmw-9432-67qq - LangGraph: Namespace labels containing `.` reach other namespaces in Postgres and SQLite stores
### Summary
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",))` 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.
### 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 deployme
MEDIUM
Severity & confidence
Source severitymedium
Platform severitymedium
Confidencehigh
Exploitationunknown
CVSS-
Affected
Vendorslanggraph-checkpoint-postgreslanggraph-checkpoint-sqlite
Productslanggraph-checkpoint-postgreslanggraph-checkpoint-sqlite
Reporting sources (2)
GitHub Security Advisories
NIST NVD - National Vulnerability Database
Timeline & provenance
Published2026-10-23T22:06:44
Last updated2026-10-27T20:53:31
Ingested2026-10-23T22:19:50
FreshnessNEAR-REAL-TIME
Threat typeadvisory
Recommended action
Review the advisory and upgrade affected packages to the first patched version.
Next steps
- Identify affected systems in your environment.
- Apply the vendor patch or mitigation guidance.
- Review logs for indicators described in the advisory.
- Follow the affected vendor/product to track updates.
Confidence explanation
Reported by a government or cert-grade source (CISA, NCSC, NVD, ENISA, MSRC).
Source type: vendor ยท Original: GitHub Security Advisories