p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in langgraph-checkpoint-sqlite

In den letzten 30 Tagen veröffentlichte Sicherheitslücken für langgraph-checkpoint-sqlite: 1. Davon im KEV-Katalog: 0.

RSS ↗
Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 5

  1. CVE-2026-115883

    Mittel · CVSS 6EPSS 0,41%Korrektur verfügbar

    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

    • Auf 3.1.2 aktualisieren
    Veröffentlicht Aktualisiert
  2. CVE-2026-71433

    Mittel · CVSS 5.3EPSS 0,36%Korrektur verfügbar

    LangGraph: Namespace prefix matching crosses segment boundaries in Postgres and SQLite stores

    LangGraph Checkpoint Postgres and SQLite Checkpoint are the Postgres and SQLite implementations of LangGraph's checkpoint saver. Prior to 3.1.1, the langgraph-checkpoint-postgres and langgraph-checkpoint-sqlite packages persisted hierarchical namespaces as a dot joined string and scoped reads by matching that string as a simple prefix pattern, so a read scoped to one namespace could also match a sibling namespace whose flattened form shares the same leading characters, or a namespace label containing unescaped pattern metacharacters, allowing an authenticated caller to retrieve stored items belonging to another tenant or user through an ordin

    • Auf 3.1.1 aktualisieren
    Veröffentlicht Aktualisiert
  3. CVE-2025-67644

    Hoch · CVSS 7.3EPSS 2,31%Korrektur verfügbar

    LangGraph SQLite Checkpoint is vulnerable to SQL Injection via metadata filter key in checkpointer list method

    LangGraph SQLite Checkpoint is an implementation of LangGraph CheckpointSaver that uses SQLite DB (both sync and async, via aiosqlite). Versions 3.0.0 and below are vulnerable to SQL injection through the checkpoint implementation. Checkpoint allows attackers to manipulate SQL queries through metadata filter keys, affecting applications that accept untrusted metadata filter keys (not just filter values) in checkpoint search operations. The _metadata_predicate() function constructs SQL queries by interpolating filter keys directly into f-strings without validation. This issue is fixed in version 3.0.1.

    • Auf 3.0.1 aktualisieren
    Veröffentlicht Aktualisiert
  4. CVE-2025-64104

    Hoch · CVSS 7.3EPSS 0,24%Korrektur verfügbar

    LangGraph SQLite Checkpoint Filter Key SQL Injection POC for SqliteStore

    LangGraph SQLite Checkpoint is an implementation of LangGraph CheckpointSaver that uses SQLite DB (both sync and async, via aiosqlite). Prior to 2.0.11, LangGraph's SQLite store implementation contains SQL injection vulnerabilities using direct string concatenation without proper parameterization, allowing attackers to inject arbitrary SQL and bypass access controls. This vulnerability is fixed in 2.0.11.

    • Auf 2.0.11 aktualisieren
    Veröffentlicht Aktualisiert
  5. CVE-2025-8709

    Hoch · CVSS 7.3EPSS 0,22%Korrektur verfügbar

    SQL Injection in langchain-ai/langchain

    A SQL injection vulnerability exists in the langchain-ai/langchain repository, specifically in the LangGraph's SQLite store implementation. The affected version is langgraph-checkpoint-sqlite 2.0.10. The vulnerability arises from improper handling of filter operators ($eq, $ne, $gt, $lt, $gte, $lte) where direct string concatenation is used without proper parameterization. This allows attackers to inject arbitrary SQL, leading to unauthorized access to all documents, data exfiltration of sensitive fields such as passwords and API keys, and a complete bypass of application-level security filters.

    • Auf 2.0.11 aktualisieren
    Veröffentlicht Aktualisiert

Prüfen Sie Ihren Server

Gleichen Sie Ihren installierten Stack und seine Versionen mit den aktuellen Sicherheitsmeldungen ab.

Prüfen Sie Ihren Server →