https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 26 Oct 2026 21:47:58 +0000 https://db.gcve.eu/vuln/fkie_cve-2026-115883 <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 &#34;.&#34;.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&#39;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> <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 &#34;.&#34;.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&#39;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> https://db.gcve.eu/vuln/fkie_cve-2026-115883 https://db.gcve.eu/vuln/ghsa-6hmw-9432-67qq <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 `(&#34;tenant&#34;, &#34;bob&#34;)` and `(&#34;tenant.bob&#34;,)` 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 `&#34;.&#34;.join(namespace)`, so a label containing `.` resolved to the namespace whose labels it spells out:</p> <p>- `get((&#34;tenant.bob&#34;,), key)`, `search((&#34;tenant.bob&#34;,))` and `list_namespaces(prefix=(&#34;tenant.bob&#34;,))` returned data stored under `(&#34;tenant&#34;, &#34;bob&#34;)`. - `delete((&#34;tenant.alice&#34;,), key)` deleted the item stored under `(&#34;tenant&#34;, &#34;alice&#34;)`. - `batch([PutOp((&#34;tenant.bob&#34;,), key, value)])` overwrote the item stored under `(&#34;tenant&#34;, &#34;bob&#34;)`.</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> <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 `(&#34;tenant&#34;, &#34;bob&#34;)` and `(&#34;tenant.bob&#34;,)` 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 `&#34;.&#34;.join(namespace)`, so a label containing `.` resolved to the namespace whose labels it spells out:</p> <p>- `get((&#34;tenant.bob&#34;,), key)`, `search((&#34;tenant.bob&#34;,))` and `list_namespaces(prefix=(&#34;tenant.bob&#34;,))` returned data stored under `(&#34;tenant&#34;, &#34;bob&#34;)`. - `delete((&#34;tenant.alice&#34;,), key)` deleted the item stored under `(&#34;tenant&#34;, &#34;alice&#34;)`. - `batch([PutOp((&#34;tenant.bob&#34;,), key, value)])` overwrote the item stored under `(&#34;tenant&#34;, &#34;bob&#34;)`.</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> https://db.gcve.eu/vuln/ghsa-6hmw-9432-67qq