CVE-2025-67644: Langgraph checkpoint sqlite SQL Injection Vulnerability
HIGHCVE-2025-67644 is a HIGH (CVSS 7.3) sql injection vulnerability (CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')) affecting Langgraph checkpoint sqlite libraries in the PyPI ecosystem. The issue involves langgraph's sqlite is vulnerable to sql injection via metadata filter key in sqlite checkpointer list method. Remediation is available by upgrading affected packages to version 3.0.1.
CVE-2025-67644 at a Glance
Security Impact
CVSS: 7.3
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N).
How to Fix CVE-2025-67644
To remediate this vulnerability, upgrade all affected Langgraph checkpoint sqlite dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
pip install langgraph-checkpoint-sqlite>=3.0.1
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
pip show langgraph-checkpoint-sqlite
How to Check if You Are Affected
To determine whether your Python environment is affected by CVE-2025-67644, inspect your installed packages using pip:
pip show langgraph-checkpoint-sqlite
Analyze the terminal output to locate any version of Langgraph checkpoint sqlite in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.0.1), your application is affected.
Note: The pip show langgraph-checkpoint-sqlite command checks currently installed packages in your active Python environment.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection'), where the product constructs all or part of an sql command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended sql command when it is sent to a downstream component. without sufficient removal or quoting of sql syntax in user-controllable inputs, the generated sql query can cause those inputs to be interpreted as sql instead of ordinary user data. In Langgraph checkpoint sqlite, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2025-67644 Affected Langgraph checkpoint sqlite Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
langgraph-checkpoint-sqlite
|
PyPI |
< 3.0.1
|
3.0.1
|
References
Frequently Asked Questions
What is CVE-2025-67644?
Which Langgraph checkpoint sqlite versions are affected?
What version fixes CVE-2025-67644?
Is langgraph-checkpoint-sqlite affected?
What is the CVSS score of CVE-2025-67644?
What CWE is associated with CVE-2025-67644?
How can I check PyPI dependencies for CVE-2025-67644?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-9rwj-6rc7-p77c",
"modified" : "2025-12-11T15:49:44Z",
"published" : "2025-12-10T00:02:21Z",
"aliases" : [ "CVE-2025-67644" ],
"summary" : "LangGraph's SQLite is vulnerable to SQL injection via metadata filter key in SQLite checkpointer list method",
"details" : "# Context\n\nA SQL injection vulnerability exists in LangGraph's SQLite checkpoint implementation that allows attackers to manipulate SQL queries through metadata filter keys. This affects applications that accept **untrusted metadata filter keys** (not just filter values) in checkpoint search operations.\n\n# Impact\n\nAttackers who control metadata filter keys can execute arbitrary sql queries against the database.\n\n# Root Cause\n\nThe `_metadata_predicate()` function constructs SQL queries by interpolating filter keys directly into f-strings without validation:\n\n```python\n# VULNERABLE CODE (before fix)\nfor query_key, query_value in metadata_filter.items():\n operator, param_value = _where_value(query_value)\n predicates.append(\n f\"json_extract(CAST(metadata AS TEXT), '$.{query_key}') {operator}\"\n )\n param_values.append(param_value)\n```\n\nWhile filter **values** are parameterized, filter **keys** are not validated, allowing SQL injection.\n\n# Attack Example\n\n**Before Fix:**\n```python\nfrom langgraph.checkpoint.sqlite import SqliteSaver\n\nsaver = SqliteSaver.from_conn_string(\"checkpoints.db\")\n\n# Attacker controls the filter keys\nmalicious_filter = {\"x') OR '1'='1\": \"dummy\"}\n\n# Returns ALL checkpoints, bypassing filtering\nresults = list(saver.list(None, filter=malicious_filter))\n```\n\n**Resulting SQL:**\n```sql\nWHERE json_extract(CAST(metadata AS TEXT), '$.x') OR '1'='1') = ?\n-- Injected condition makes WHERE clause always true\n```\n\n## Who Is Affected?\n\n### LangSmith Deployment Customers: NOT Impacted\n\n**LangSmith deployment customers are NOT affected by this vulnerability.** LangSmith deployments do not allow configuring custom checkpointers, so the vulnerable code path cannot be reached.\n\n### High Risk: Custom Server Deployments\n\nYou are affected if your application:\n- Runs a custom server with SqliteSaver checkpointer\n- Exposes an endpoint for fetching checkpoint history (e.g., via `get_state_history()`)\n- Accepts metadata filter keys from untrusted sources\n\n**Example vulnerable code:**\n```python\n# Custom server endpoint - User controls filter key names - DANGEROUS\n@app.post(\"/api/history\")\ndef get_history(request):\n filter_field = request.json.get(\"filter_field\") # Untrusted input\n filter_value = request.json.get(\"filter_value\")\n\n # VULNERABLE: Attacker can bypass access controls\n history = list(graph.get_state_history(\n config,\n filter={filter_field: filter_value}\n ))\n return history\n```\n\n**Note on privilege escalation:** If an endpoint allows end users to specify arbitrary filter keys, those users likely already have legitimate access to query the checkpoint database. In such cases, this vulnerability may not constitute a privilege escalation, as users who can control filter keys would typically already be expected to have database access. However, the SQL injection still allows bypassing intended filtering logic and metadata-based access controls that the application may rely on for data isolation.\n\n### Additional Security Hardening (Defense in Depth)\n\nThis release also includes hardening improvements:\n\n**1. Checkpoint Limit Parameter**: used f-string interpolation into parameterized query. Not considered a vulnerability as it requires users to accept untrusted input and not validate it against the actual API signature. \n\n**2. Store Filter Value Parameterization**: Refactored all filter value handling from manual quote escaping to parameterized queries\n\n## Remediation\n\n### Immediate Actions\n\n1. **Update to the patched version** of `langgraph-checkpoint-sqlite`\n2. **Audit your code** for locations where filter keys come from untrusted sources",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "PyPI",
"name" : "langgraph-checkpoint-sqlite"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "3.0.1"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/langchain-ai/langgraph/security/advisories/GHSA-9rwj-6rc7-p77c"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-67644"
}, {
"type" : "WEB",
"url" : "https://github.com/langchain-ai/langgraph/commit/297242913f8ad2143ee3e2f72e67db0911d48e2a"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/langchain-ai/langgraph"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-89" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2025-12-10T00:02:21Z",
"nvd_published_at" : "2025-12-11T00:16:23Z"
}
}