CVE Intelligence
Medium Input validation

CVE-2026-115883 — LangGraph: Namespace labels containing `.` reach other namespaces in Postgres and SQLite stores

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.

Published Oct 23, 2026 · Updated Oct 26, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: GitHub_M

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.3% (30-day exploitation probability)+3
  • Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.3%
ahead of 22% of scored CVEs · Oct 29, 2026
Affects
Langchain-ai
Langgraph and 2 more
CVSS base
6.0
Medium · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Pip Langgraph-checkpoint-sqlite: fixed in version 3.1.2 — github.com (GitHub Security Advisories)
  • Pip Langgraph-checkpoint-postgres: fixed in version 3.1.3 — github.com (GitHub Security Advisories)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Langchain-ai Langgraph, Langchain-ai Langgraph-checkpoint-postgres, Langchain-ai Langgraph-checkpoint-sqlite…).
  2. Apply the fixed version or the patch documented under Remediation.
  3. Search available logs for exploit probes matching the vulnerability class (input validation), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Langchain-ai Langgraph version < 1.2.15 Vulnerable CVE Program (cve.org) e CISA ADP
Langchain-ai Langgraph-checkpoint-postgres version < 3.1.3 Vulnerable CVE Program (cve.org) e CISA ADP
Langchain-ai Langgraph-checkpoint-sqlite version < 3.1.2 Vulnerable CVE Program (cve.org) e CISA ADP
Pip Langgraph-checkpoint-postgres < 3.1.3 Vulnerable GitHub Security Advisories
Pip Langgraph-checkpoint-sqlite < 3.1.2 Vulnerable GitHub Security Advisories

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Attack requirements
Present
Privileges required
Low
User interaction
None
Scope
X
Confidentiality (vulnerable system)
High
Integrity (vulnerable system)
Low
Availability (vulnerable system)
None
Confidentiality (subsequent)
None
Integrity (subsequent)
None
Availability (subsequent)
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
6.0 CVSS 4.0 Medium — — security-advisories@github.com via NIST National Vulnerability Database
6.0 CVSS 4.0 Medium — — GitHub_M via CVE Program (cve.org) e CISA ADP
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X (score shown at the top: security-advisories@github.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-20 · Improper Input Validation

Other CVEs with this weakness →

EPSS over time FIRST

Oct 24, 2026 → Oct 29, 2026 · 6 reading(s) · max 0.41%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

  • 2026
  • SSVC assessment updated
    Oct 26, 2026 · CVE Program (cve.org) e CISA ADP
  • Source status changed · Received → Awaiting Analysis
    Oct 26, 2026 · NIST National Vulnerability Database
  • Fix documented
    Oct 23, 2026 · GitHub Security Advisories
  • Affected products added · pip/langgraph-checkpoint-postgres, pip/langgraph-checkpoint-sqlite
    Oct 23, 2026 · GitHub Security Advisories
  • Affected products added · langchain-ai/langgraph, langchain-ai/langgraph-checkpoint-postgres, langchain-ai/langgraph-checkpoint-sqlite
    Oct 23, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 23, 2026
  • CVSS changed · 6.0
    Oct 23, 2026 · NIST National Vulnerability Database
  • Source status changed · → Received
    Oct 23, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 23, 2026 · NIST National Vulnerability Database
  • CVE published
    Oct 23, 2026 · GitHub_M

Source activity

Repeated readings are counted rather than listed.

  • 1× References added · Oct 23, 2026 – Oct 23, 2026
  • 1× Official description updated · Oct 23, 2026 – Oct 23, 2026

References

6 on the record

Elsewhere on this site

Langchain-ai
every CVE for this vendor
Input validation
same class
CWE-20
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-118667 LangGraph: Unencoded identifiers in LangGraph SDK v3 streaming can redirect authenticated GET requests 1d
  • CVE-2026-115885 LangGraph CLI prints the registry push token in `langgraph deploy --verbose` output 6d
  • CVE-2026-104873 LangGraph SDK custom auth silently ignores actions= on resource decorators 27d
  • CVE-2026-71433 LangGraph: Namespace prefix matching crosses segment boundaries in Postgres and SQLite stores Aug 6, 2026
  • CVE-2026-14742 langchain-ai langgraph Task Result Cache _cache.py _freeze weak hash Jul 5, 2026
  • CVE-2026-48775 LangGraph Checkpoint: Unsafe JSON deserialization in checkpoint loading Jun 16, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-115883 is "LangGraph: Namespace labels containing `.` reach other namespaces in Postgres and SQLite stores", rated Medium. It affects Langgraph (Langchain-ai); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 6.0 describes technical severity. EPSS 0.30% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.