Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-71433 medium CVSS 5.3

Information Disclosure in langgraph-checkpoint-postgres (CVE-2026-71433)

Summary

Vulnerability in langgraph-checkpoint-postgres (CVE-2026-71433). Confidential information can be exposed externally. Exploitable via memories.alice. Mitigation: upgrade to 3.1.1 or later.

Original description

The description as published by the source.

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 '%'. Because LIKE has no notion of the . separator, a scoped search or list_namespaces 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 are fixed-length identifiers such as UUIDs, containing no _ or %, are not affected — no such label can be a prefix of another. InMemoryStore compares namespaces element-wise and is not affected.

Three distinct cases were possible:

  • Sibling namespaces. A read scoped to ("foo",) also returned items under ("foobar",) and ("foo2",).
  • Unescaped pattern metacharacters. _ and % are legal namespace labels — only . is rejected — but…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-71433 has been found in langgraph-checkpoint-postgres.
Attackers can target a specific entry point like memories.alice over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 5.3/10.
What to do: upgrade langgraph-checkpoint-postgres to 3.1.1 or later.
If unsure, ask your IT team or search "langgraph-checkpoint-postgres CVE-2026-71433" on the vendor's site.

CVE-2026-71433 (langgraph-checkpoint-postgres) — CWE-200 / CVSS v3 5.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: memories.alice / LIKE / search / list_namespaces
Patched: 3.1.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Information disclosure (CWE-200) exists in langgraph-checkpoint-postgres. Attackers reach the vulnerable code path via memories.alice.

📍 Affected scope

Check the vendor advisory for the affected versions of langgraph-checkpoint-postgres. Attack surface: memories.alice / LIKE / search / list_namespaces.

🔥 Severity

Severity: Medium (CVSS 5.3/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 3.1.1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'langgraph-checkpoint-postgres' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'langgraph-checkpoint-postgres' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で langgraph-checkpoint-postgres を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade langgraph-checkpoint-postgres to 3.1.1

    ステージング環境で 3.1.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

pip langgraph-checkpoint-postgres
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.1.1"}]}]
pip langgraph-checkpoint-sqlite
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.1.1"}]}]
PyPI langgraph-checkpoint-postgres
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.1.1"}]}]
PyPI langgraph-checkpoint-sqlite
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.1.1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details