Skip to main content
VulnerabilityPublished

CVE-2026-71433: langchain-ai langgraph · Information Exposure

Affects langchain-ai langgraphSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.3 Medium : upgrade to 3.1.1 when convenient.

Data as of 5 Nov 2026, 00:01 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.1.1
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade langgraph and langgraph-checkpoint-sqlite and langgraph-checkpoint-postgres to 3.1.1.

Affected software

ProductAffectedFixed in
langchain-ailanggraphAffected
  • <3.1.1
Fixed in
  • 3.1.1
langchain-ailanggraph-checkpoint-sqliteAffected
  • <3.1.1
Fixed in
  • 3.1.1
langchain-ailanggraph-checkpoint-postgresAffected
  • <3.1.1
Fixed in
  • 3.1.1

AI-suggested

Upgrade langgraph-checkpoint-postgres and langgraph-checkpoint-sqlite to version 3.1.1 or later, where the issue is fixed. Patch status is confirmed by the vendor advisory indicating the fix in version 3.1.1.

Description

A vulnerability in langgraph's checkpoint saver implementations for Postgres and SQLite allows an authenticated user to access stored items belonging to other tenants or users due to improper namespace scoping. This occurs because hierarchical namespaces are persisted as dot-joined strings and reads are scoped by prefix matching, which can overlap with sibling namespaces or those containing unescaped pattern metacharacters. The issue affects versions prior to 3.1.1 and is fixed in version 3.1.1.

References

Community reviews

Loading reviews…