Skip to content

← Actionable
Medium, CVSS 5.3

LangGraph: Namespace prefix matching crosses segment boundaries in Postgres and SQLite stores

CVE-2026-71433GHSA-47pj-3jcm-6whg

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (langgraph-checkpoint-postgres 3.1.1; langgraph-checkpoint-sqlite 3.1.1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.3 · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS
  • CVE-2026-71433: 0.36% estimated exploitation activity in the next 30 days; percentile 30.20 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary The Postgres and SQLite stores persist hierarchical namespaces as a dot-joined string (("memories", "alice") becomes memories.alice) and scoped reads by matching that string with LIKE '<path%'. Because LIKE has no notion of the . separator, a scoped search or listnamespaces also matched sibling namespaces whose flattened form shares leading characters. Applications commonly use the namespace as a tenant boundary. Where they do, a read scoped to one namespace could return items belonging to another, without any crafted input — an ordinary scoped request was sufficient. We have no evidence of this behavior being exploited in the wild. Affected users / systems You may be affected if you: - use PostgresStore/AsyncPostgresStore or SqliteStore/AsyncSqliteStore, and - rely on the namespace to separate data between users or tenants, and - have namespace labels where one is a prefix of another (1 and 12, alice and alice2), or labels containing or % Applications whose namespace labels…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-47pj-3jcm-6whg

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-71433

Advisory: LangGraph: Namespace prefix matching crosses segment boundaries in Postgres and SQLite stores
IDs: CVE-2026-71433, GHSA-47pj-3jcm-6whg
Record: https://patchnext.com/advisories/cve-2026-71433 (revision 1, source checked 26 Oct 2026, 13:50 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: langgraph-checkpoint-postgres 3.1.1; langgraph-checkpoint-sqlite 3.1.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI langgraph-checkpoint-postgres: affected < 3.1.1; fixed in 3.1.1
- PyPI langgraph-checkpoint-sqlite: affected < 3.1.1; fixed in 3.1.1

## Suggested inspection (read-only)
- `python -m pip show langgraph-checkpoint-postgres`: prints the installed version. Run with the environment that serves production active.
- `python -m pip show langgraph-checkpoint-sqlite`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on langgraph-checkpoint-postgres, langgraph-checkpoint-sqlite.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-47pj-3jcm-6whg (GitHub-reviewed advisory GHSA-47pj-3jcm-6whg lists affected ranges: PyPI langgraph-checkpoint-postgres >=0 =0 <3.1.1)

Commands are suggestions: review each one before running it.

Loading voting…