cve.bz

CVE-2026-115883 langchain-ai: Incorrect Authorization

6.0 mediumEPSS 0.3%Fix available

Medium (6.0) in langchain-ai. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in langgraph-checkpoint-postgres 3.1.3.

On this page
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.

Severity

CVSS 4.0

6.0 medium
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N
EPSS
0.3% (unchanged from 0.3% a week ago) estimated probability of exploitation activity in the next 30 days; 23rd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-26. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-20 Improper Input Validation
CWE-863 Incorrect Authorization
OWASP Top 10
A01:2025 Broken Access Control, A05:2025 Injection
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • langgraph-checkpoint-postgres (PyPI): fixed in 3.1.3
  • langgraph-checkpoint-sqlite (PyPI): fixed in 3.1.2

Ask an AI about this CVE

Show the promptExplain CVE-2026-115883 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-115883?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-115883?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-115883 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
langchain-ai langgraph< 1.2.15
langchain-ai langgraph-checkpoint-postgres< 3.1.3
langchain-ai langgraph-checkpoint-sqlite< 3.1.2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-6hmw-9432-67qqPyPIlanggraph-checkpoint-postgres<3.1.33.1.3
GHSA-6hmw-9432-67qqPyPIlanggraph-checkpoint-sqlite<3.1.23.1.2

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-20 (51).

References

Check your stackJSON