Browse / AI Framework and Platform Flaws / SQL and query injection
SQL and query injection
22 records in AI Framework and Platform Flaws.
- Kubeflow Pipelines: SQL injection through unvalidated pagination tokens in Kubeflow Pipelines API server Crafted base64 pagination tokens inject SQL through unvalidated identifier fields in list API calls, letting attackers read database rows across namespaces.
- n8n: Snowflake Node executeQuery Operation Allows SQL Injection via Unparameterized Expression Interpolation Expression values from workflow data are concatenated into a raw Snowflake SQL string instead of bound as parameters, so attacker data can alter the query.
- n8n: MySQL v1 Node executeQuery Operation Allows SQL Injection via Unparameterized Expression Interpolation Expression values from webhook input are concatenated into a raw MySQL query in the legacy node, letting attacker-supplied SQL run.
- n8n: PostgresTrigger Node SQL Injection Allows Authenticated Users to Execute Arbitrary SQL on Connected PostgreSQL Instances Unescaped channel, function and trigger names let an authenticated user run arbitrary SQL against the connected database.
- n8n: SQL Injection in Postgres v1/TimesclaeDB Nodes Parameters for the Postgres and TimescaleDB workflow nodes are concatenated into SQL, letting a workflow author run arbitrary queries on the connected database.
- n8n: NoSQL Injection in MongoDB Node Find And Replace Operation An unvalidated filter value lets a workflow editor match and overwrite MongoDB documents beyond the intended set.
- n8n Has a Source Control Pull SQL Injection A malicious Data Table JSON file committed to a connected Git repository carries a crafted column name that injects SQL when an administrator runs Source Control Pull.
- n8n has SQL Injection in Snowflake and MySQL Nodes Table, column and update-key identifiers are interpolated into SQL in the Snowflake and legacy MySQL nodes, a gap the earlier fix did not cover.
- n8n has SQL Injection in SeaTable Node Unescaped user input concatenated into SeaTable row search queries lets an attacker alter the query and retrieve rows the workflow meant to filter out.
- n8n has SQL Injection in Oracle Database Node via Limit Field Input flowing through an expression into the Oracle node's Limit field is concatenated into the SQL query, letting webhook-triggered attackers run arbitrary queries.
- LiteLLM has SQL Injection in Proxy API key verification An Authorization header value is concatenated into a key-verification query on error paths, so unauthenticated requests can inject SQL against the proxy database.
- PraisonAI: SQL Injection via unvalidated `table_prefix` in 9 conversation store backends (incomplete fix for CVE-2026-40315) The table prefix is interpolated into SQL in nine store backends that lack the validation added to the SQLite store, so crafted prefixes inject queries.
- PraisonAI: SQLiteConversationStore didn't validate table_prefix when constructing SQL queries The table prefix from configuration is concatenated into SQL identifiers without validation, letting injected fragments read internal tables.
- PraisonAI Has Second-Order SQL Injection in `get_all_user_threads` A thread ID stored with a crafted SQL fragment is later concatenated unescaped into a thread-listing query, executing injected SQL against the database.
- n8n has SQL Injection in Data Table Node via orderByColumn Expression Expressions in the Data Table Get node's orderByColumn field are concatenated into SQL, letting authenticated workflow editors inject queries.
- n8n: SQL Injection in MySQL, PostgreSQL, and Microsoft SQL nodes Database workflow nodes do not escape table and column identifiers, so a crafted name in node configuration injects arbitrary SQL.
- LangGraph's SQLite is vulnerable to SQL injection via metadata filter key in SQLite checkpointer list method Metadata filter keys are concatenated into SQL in the SQLite checkpointer's list method, so a crafted key injects arbitrary query logic.
- LangGraph SQLite Checkpoint Filter Key SQL Injection POC for SqliteStore Filter keys taken from user input are concatenated into a JSON path inside a SQL query without escaping, allowing injected SQL.
- LangGraph's SQLite store implementation has a SQL Injection Vulnerability Filter operator handling concatenates input into SQL in the SQLite checkpoint store, so crafted filters can read other records and stored secrets.
- FlowiseDB vulnerable to SQL Injection by authenticated users An authenticated user imports a crafted chatflow file whose ID contains traversal and SQL-breaking input, which the import routine concatenates into a raw SQL query.
- SQL injection in litellm The team update route places the user_id value directly into a raw SQL delete statement, letting attackers run blind queries to extract stored keys and tokens.
- SQL injection in litellm The /global/spend/logs endpoint concatenates the api_key query parameter directly into a SQL statement instead of using parameters.