CVE-2026-33713

n8n is an open source workflow automation platform. Prior to versions 2.14.1, 2.13.3, and 1.123.26, an authenticated user with permission to create or modify workflows could exploit a SQL injection vulnerability in the Data Table Get node. On default SQLite DB, single statements can be manipulated and the attack surface is practically limited. On PostgreSQL deployments, multi-statement execution is possible, enabling data modification and deletion. The issue has been fixed in n8n versions 1.123.26, 2.13.3, and 2.14.1. Users should upgrade to one of these versions or later to remediate the vulnerability. If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Limit workflow creation and editing permissions to fully trusted users only, disable the Data Table node by adding `n8n-nodes-base.dataTable` to the `NODES_EXCLUDE` environment variable, and/or review existing workflows for Data Table Get nodes where `orderByColumn` is set to an expression that incorporates external or user-supplied input. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

An attacker with a legitimate n8n account (e.g., a contractor, compromised internal credential, or over-privileged developer) creates or modifies a workflow containing a Data Table Get node. They set the orderByColumn parameter to an expression that injects SQL: e.g., id; DROP TABLE ai_training_data; -- or a UNION-based payload to extract API keys from n8n's own credentials table. On a PostgreSQL backend, the injected multi-statement payload executes directly, allowing the attacker to exfiltrate LLM API keys, Stripe webhooks, or database credentials stored in n8n's encrypted credential store—then pivot to connected AI infrastructure. The attack leaves minimal trace if audit logging is not enabled on the DB layer.