Is CVE-2026-71433 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-71433 being exploited in the wild.

How severe is CVE-2026-71433?

Medium severity, with a CVSS score of 5.3, published 6 August 2026.

Which products and versions are affected?

langgraph-checkpoint-postgres (PyPI) < 3.1.1, ECOSYSTEM:introduced=0,fixed=3.1.1; langgraph-checkpoint-sqlite (PyPI) < 3.1.1, ECOSYSTEM:introduced=0,fixed=3.1.1.

Is there a fix for CVE-2026-71433?

Yes. langgraph-checkpoint-postgres (PyPI): upgrade to 3.1.1 or later; langgraph-checkpoint-sqlite (PyPI): upgrade to 3.1.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-71433 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-71433?

Check whether you run langgraph-checkpoint-postgres (PyPI) or langgraph-checkpoint-sqlite (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-71433: LangGraph incorrect authorization in Postgres and SQLite namespace matching

Q: Is there a fix for CVE-2026-71433?

Yes. langgraph-checkpoint-postgres (PyPI): upgrade to 3.1.1 or later; langgraph-checkpoint-sqlite (PyPI): upgrade to 3.1.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-71433 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-71433?

Check whether you run langgraph-checkpoint-postgres (PyPI) or langgraph-checkpoint-sqlite (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-71433 · Severity: medium · CVSS 5.3 · Published 2026-08-06

LangGraph is a library used to build stateful AI agents. A flaw in how it handles data storage in Postgres and SQLite databases could allow one user or tenant to see data belonging to another if their identifiers share similar names (e.g., 'user1' seeing data for 'user12'). This could lead to unauthorized access to sensitive conversation history or agent memory in multi-tenant applications.

Technologies: langgraph-checkpoint-sqlite (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2026-71433 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-71433 being exploited in the wild.
How severe is CVE-2026-71433?: Medium severity, with a CVSS score of 5.3, published 6 August 2026.
Which products and versions are affected?: langgraph-checkpoint-postgres (PyPI) < 3.1.1, ECOSYSTEM:introduced=0,fixed=3.1.1; langgraph-checkpoint-sqlite (PyPI) < 3.1.1, ECOSYSTEM:introduced=0,fixed=3.1.1.
Is there a fix for CVE-2026-71433?: Yes. langgraph-checkpoint-postgres (PyPI): upgrade to 3.1.1 or later; langgraph-checkpoint-sqlite (PyPI): upgrade to 3.1.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-71433 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-71433?: Check whether you run langgraph-checkpoint-postgres (PyPI) or langgraph-checkpoint-sqlite (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

langgraph-checkpoint-postgres (PyPI): upgrade to 3.1.1 or later
```
pip install "langgraph-checkpoint-postgres>=3.1.1"
```
langgraph-checkpoint-sqlite (PyPI): upgrade to 3.1.1 or later
```
pip install "langgraph-checkpoint-sqlite>=3.1.1"
```

Technical details

The Postgres and SQLite store implementations in LangGraph persist hierarchical namespaces as dot-joined strings (e.g., 'memories.alice'). Scoped read operations like 'search' and 'list_namespaces' used SQL 'LIKE' patterns (e.g., 'path%') for matching. Because 'LIKE' does not recognize the dot separator, a query for 'foo' would incorrectly match 'foobar' or 'foo2'. Additionally, the implementation failed to escape SQL metacharacters like '_' and '%', allowing them to act as wildcards. This results in an authorization bypass where a user scoped to one namespace can retrieve items from another. The issue is fixed in version 3.1.1 by implementing segment-aware matching and proper character escaping.

Affected products

LangChain AI langgraph-checkpoint-postgres < 3.1.1
LangChain AI langgraph-checkpoint-sqlite < 3.1.1

Identifiers

CVE-2026-71433
GHSA-47pj-3jcm-6whg
PYSEC-2026-3635
PYSEC-2026-3636

Timeline

2026-07-30: patched: Fix merged into main branch
2026-08-06: advisory: GitHub Advisory published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.