GHSA-47pj-3jcm-6whg: LangGraph: Namespace prefix matching crosses segment boundaries in Postgres and SQLite stores

Summary

The Postgres and SQLite stores in LangGraph matched scoped namespace reads with LIKE on a dot-joined string, so a scoped search or list_namespaces could also return items from sibling namespaces that share leading characters, such as foo and foobar. Namespace labels containing _ or % were also interpreted as pattern metacharacters, letting user_1 match userX1, and the list_namespaces suffix condition could match sibling leaves like users.malice. The flaw is a confidentiality issue in read paths only where namespaces serve as a tenant or user boundary, and the source reports no evidence of exploitation in the wild.

Mitigation

Upgrade to langgraph-checkpoint-postgres 3.1.1 or langgraph-checkpoint-sqlite 3.1.1. Callers relying on multi-segment * matching in list_namespaces can express it by combining prefix and suffix conditions, for example list_namespaces(prefix=["uid"], suffix=["alice"]). The source also recommends fixed-length namespace labels such as UUIDs and validating user-supplied labels at the boundary.

Related items

• MediumGHSA-8prr-f582-jqq3: LangGraph CLI prints the registry push token in `langgraph deploy --verbose` outputSame vendor · GitHub Advisory Database
• HighGHSA-4hm6-w6qq-w73v: LangGraph JavaScript custom authentication may permit cross-user Store accessSame vendor · GitHub Advisory Database
• MediumGHSA-3fx2-cqw9-xr3c: LangGraph: Unencoded identifiers in LangGraph SDK v3 streaming can redirect authenticated GET requestsSame vendor · GitHub Advisory Database
• MediumGHSA-6hmw-9432-67qq: LangGraph: Namespace labels containing `.` reach other namespaces in Postgres and SQLite storesSame vendor · GitHub Advisory Database
• MediumCVE-2026-108575: BerriAI LiteLLM improper authorization in secret resolution via api_keySame vendor · NVD/CVE Database