<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-26T21:47:57.926542+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/fkie_cve-2026-115883</id>
    <title>fkie_cve-2026-115883</title>
    <updated>2026-10-26T21:47:57.927874+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-115883"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-6hmw-9432-67qq</id>
    <title>GHSA-6hmw-9432-67qq — LangGraph: Namespace labels containing `.` reach other namespaces in Postgres and SQLite stores</title>
    <updated>2026-10-26T21:47:57.927935+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: langgraph-checkpoint-postgres, PyPI: langgraph-checkpoint-sqlite</p>
<p>### Summary</p>
<p>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.</p>
<p>### Details</p>
<p>`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:</p>
<p>- `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")`.</p>
<p>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.</p>
<p>### Impact</p>
<p>You may be affected if you use one of these stores, rely on namespaces to keep users or tenants apart, and…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-6hmw-9432-67qq"/>
  </entry>
</feed>
