KEVWire

Security intelligence, with context.

Response snapshot Oct 27, 2026, 01:06 UTC

Back to the wire
Permalink
VulnerabilityCVE-2026-115883

LangGraph: Namespace labels containing `.` reach other namespaces in Postgres and SQLite stores

The Postgres and SQLite stores save a namespace as its labels joined with `.`, so `("tenant", "bob")` and `("tenant.bob",)` map to the same stored namespace. `put` rejected labels containing `.

Published Updated

At a glance

Exploited
Not known
Severity
6.0 Medium (CVSS 4.0)
Chance of exploitation
0.3% in the next 30 days
Sources
1 source

What to do

GitHub lists first patched versions: langgraph-checkpoint-postgres: 3.1.3; langgraph-checkpoint-sqlite: 3.1.2. Confirm the affected range and upgrade guidance in the exact advisory.

Read GitHub-reviewed advisory GHSA-6hmw-9432-67qq (opens a new tab)

What happened

### Summary

The Postgres and SQLite stores save a namespace as its labels joined with `.`, so `("tenant", "bob")` and `("tenant.bob",)` map to the same stored namespace. `put` rejected labels containing `.`, but `get`, `search`, `delete`, `list_namespaces`, their async versions, and ops passed directly to `batch`/`abatch` did not. A caller that could pass such a label could read, overwrite or delete items in another namespace.

### Details

`BaseStore` checked namespace labels only in `put`/`aput`. The other methods passed the namespace on unchecked, and `batch`/`abatch` checked nothing, including the `PutOp` items inside them. `PostgresStore`, `AsyncPostgresStore`, `SqliteStore` and `AsyncSqliteStore` turn a namespace into text with `".".join(namespace)`, so a label containing `.` resolved to the namespace whose labels it spells out:

Continue reading

- `get(("tenant.bob",), key)`, `search(("tenant.bob",))` and `list_namespaces(prefix=("tenant.bob",))` returned data stored under `("tenant", "bob")`. - `delete(("tenant.alice",), key)` deleted the item stored under `("tenant", "alice")`. - `batch([PutOp(("tenant.bob",), key, value)])` overwrote the item stored under `("tenant", "bob")`.

All releases of `langgraph-checkpoint-postgres` before 3.1.3 and `langgraph-checkpoint-sqlite` before 3.1.2 are affected. `InMemoryStore` compares namespaces as tuples and is not affected.

### Impact

You may be affected if you use one of these stores, rely on namespaces to keep users or tenants apart, and let untrusted input choose a namespace label that reaches a read, delete or `batch` call. Such input could read, overwrite or delete another tenant's items. Labels written through `put` could never contain `.`, so no stored data becomes unreachable after upgrading.

LangSmith Deployment: the HTTP store API already rejected such labels, but store calls made from graph code reached the same flaw. The Agent Server rejects these labels from versions 0.15.5 and 0.16.2. On LangSmith Cloud, new deployments and revisions already include the fix and existing deployments get it on their next revision; self-hosted deployments should upgrade.

### Remediation

Upgrade to `langgraph-checkpoint-postgres` 3.1.3 or `langgraph-checkpoint-sqlite` 3.1.2. Both require `langgraph-checkpoint` 4.3.0, where `get`, `search`, `delete` and `list_namespaces` reject labels that are empty, are not strings, or contain `.` with `InvalidNamespaceError`, and the Postgres and SQLite stores apply the same check to every op passed to `batch`/`abatch`.

Stores outside this repository that turn namespaces into delimited text can call `langgraph.store.base.validate_op_namespace` for each op they run.

Affected package ranges reported by GitHub: langgraph-checkpoint-postgres: < 3.1.3 langgraph-checkpoint-sqlite: < 3.1.2

Scores and how they were measured

CVSS base severity

6.0

Version 4.0As of

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

Measurement source (opens a new tab)

How bad it is if exploited. Not a prediction of exploitation or proof you are exposed.

EPSS probability

0.3%

Scored Percentile 22.3%

Model and measurement source (opens a new tab)

A model's estimate of exploitation in the next 30 days, not certainty or your own risk.

Related technology

Sources

  1. Primary source

    GitHub-reviewed advisory GHSA-6hmw-9432-67qq (opens a new tab)

    The public advisory supplies the description, affected package/version ranges, and any listed CVSS metric. GitHub review is not local review.

    Published Checked

  2. Primary source

    GitHub public advisory API page (opens a new tab)

    The API page supplied GHSA-6hmw-9432-67qq, its actual identifiers, source dates, and structured metrics.

    Published Date not suppliedChecked

  3. Primary source

    FIRST measured EPSS score (opens a new tab)

    Measured EPSS probability and percentile for CVE-2026-115883, scored 2026-10-26. This is a model estimate, not proof of exposure.

    Published Checked

Cite this record

For factual claims, cite the primary sources above; cite KEVWire for its compilation, dates, and classifications.

APA

KEVWire. (2026, October 25). LangGraph: Namespace labels containing `.` reach other namespaces in Postgres and SQLite stores (CVE-2026-115883). https://kevwire.com/record/CVE-2026-115883

MLA

"LangGraph: Namespace labels containing `.` reach other namespaces in Postgres and SQLite stores (CVE-2026-115883)." KEVWire, 25 Oct. 2026, kevwire.com/record/CVE-2026-115883.

Chicago

KEVWire. "LangGraph: Namespace labels containing `.` reach other namespaces in Postgres and SQLite stores (CVE-2026-115883)." Last modified October 25, 2026. https://kevwire.com/record/CVE-2026-115883.

Evidence summary (plain text)

LangGraph: Namespace labels containing `.` reach other namespaces in Postgres and SQLite stores (Oct 23, 2026).
The Postgres and SQLite stores save a namespace as its labels joined with `.`, so `("tenant", "bob")` and `("tenant.bob",)` map to the same stored namespace. `put` rejected labels containing `.`, but `get`, `search`, `delete`, `list_namespaces`, their async versions, and ops passed directly to `batch`/`abatch` did not. A caller that could pass such a label could read, overwrite or delete items in another namespace.

`BaseStore` checked namespace labels only in `put`/`aput`. The other methods passed the namespace on unchecked, and `batch`/`abatch` checked nothing, including the `PutOp` items inside them. `PostgresStore`, `AsyncPostgresStore`, `SqliteStore` and `AsyncSqliteStore` turn a namespace into text with `".".join(namespace)`, so a label containing `.` resolved to the namespace whose labels it spells out:
CVSS 6.0 (version 4.0; evidence as of Oct 25, 2026; https://github.com/advisories/GHSA-6hmw-9432-67qq).
EPSS 0.3% for the following 30 days, scored Oct 26, 2026 (https://api.first.org/data/v1/epss?cve=CVE-2026-115883&date=2026-10-26).
Sources:
GitHub-reviewed advisory GHSA-6hmw-9432-67qq: https://github.com/advisories/GHSA-6hmw-9432-67qq
GitHub public advisory API page: https://api.github.com/advisories?type=reviewed&per_page=100&sort=updated&direction=desc
FIRST measured EPSS score: https://api.first.org/data/v1/epss?cve=CVE-2026-115883&date=2026-10-26
Record ID: CVE-2026-115883.
Record origin: Ingested record.
AI evidence: Not assessed.
Known exploitation: Not assessed.
Zero-day status: Not assessed. KEV membership alone does not establish zero-day status.
About this data

This record was ingested from a data source. Retrieved: Oct 26, 2026, 19:40 UTC. Ingestion is not an independent editorial investigation.

A CISA KEV listing documents known exploitation, not necessarily a zero-day; absence from the catalog does not prove a vulnerability has never been exploited.

Technology tags indicate possible relevance, not verified exposure. Confirm the affected product, version, and configuration against your own inventory; KEVWire does not scan your systems.

A personal reading checklist on this device, not verified remediation.

Record JSON

Your account

Email alerts

Email alerts are not available yet. To follow your stack today, use its RSS feed, which honors your filters, or connect an AI agent through the API.

Suggest an improvement

Ideas, missing sources, corrections, and bugs are all welcome. No account needed. Suggestions are reviewed by a person before anything changes.

Record details

Record detail