Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-67644: CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in langchain-ai langgraph

0
High
VulnerabilityCVE-2025-67644cvecve-2025-67644cwe-89
Published: Wed Dec 10 2025 (12/10/2025, 23:37:36 UTC)
Source: CVE Database V5
Vendor/Project: langchain-ai
Product: langgraph

Description

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.

AI-Powered Analysis

AILast updated: 12/11/2025, 00:08:37 UTC

Technical Analysis

CVE-2025-67644 is a SQL injection vulnerability classified under CWE-89, affecting langchain-ai's langgraph product versions prior to 3.0.1. The vulnerability arises from the CheckpointSaver component, which uses SQLite databases both synchronously and asynchronously via aiosqlite. Specifically, the _metadata_predicate() function constructs SQL queries by directly interpolating metadata filter keys into Python f-strings without any sanitization or validation. Since filter keys, not just values, are user-controllable in checkpoint search operations, an attacker can craft malicious filter keys that alter the structure of SQL queries. This can lead to unauthorized data access or leakage, impacting confidentiality and integrity. The vulnerability requires low attack complexity and only low privileges, with no user interaction needed, but local access to the application is necessary (AV:L). The scope is considered changed (S:C) because the injection can affect multiple database queries. The CVSS 3.1 base score is 7.3 (high), reflecting the significant confidentiality impact and moderate integrity impact, but no availability impact. The issue was publicly disclosed on December 10, 2025, and fixed in version 3.0.1. No known exploits have been reported in the wild yet, but the vulnerability poses a serious risk to applications relying on langgraph for checkpoint storage and search functionality.

Potential Impact

For European organizations, this vulnerability could lead to unauthorized disclosure of sensitive data stored in SQLite databases managed by langgraph, especially in AI or data processing applications that utilize the CheckpointSaver feature. Attackers with local access or the ability to influence metadata filter keys can exploit this flaw to extract confidential information or manipulate query results, undermining data integrity. This is particularly concerning for sectors handling sensitive personal data, such as finance, healthcare, and government agencies, which are subject to strict data protection regulations like GDPR. The compromise of data confidentiality could result in regulatory penalties, reputational damage, and operational disruptions. Additionally, since langgraph is used in AI workflows, the integrity of AI model checkpoints and metadata could be affected, potentially impacting AI decision-making processes. The lack of known exploits currently provides a window for mitigation, but the ease of exploitation and high impact necessitate urgent attention.

Mitigation Recommendations

European organizations should immediately upgrade langgraph to version 3.0.1 or later, where the vulnerability is fixed. Until upgrading is possible, implement strict input validation and sanitization on all metadata filter keys used in checkpoint search operations to prevent injection of malicious SQL code. Avoid accepting untrusted or user-supplied filter keys without validation. Employ application-layer security controls such as parameterized queries or prepared statements instead of string interpolation for SQL query construction. Conduct thorough code reviews and security testing focusing on all points where metadata filters are processed. Monitor application logs for unusual query patterns or errors indicative of attempted SQL injection. Restrict local access to systems running langgraph to trusted users only, minimizing the attack surface. Finally, integrate vulnerability scanning and penetration testing into the development lifecycle to detect similar injection flaws proactively.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2025-12-09T18:36:41.330Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 693a0800e425ca5072db0c66

Added to database: 12/10/2025, 11:53:36 PM

Last enriched: 12/11/2025, 12:08:37 AM

Last updated: 12/11/2025, 1:19:29 AM

Views: 45

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats