Monitor vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
5.3
n8n: Attackers can inject malicious database queries
GHSA-f3f2-mcxc-pwjx
Summary
If you use n8n to manage workflows that connect to a database, an attacker with permission to create workflows could inject malicious database commands by entering special characters in the database configuration. This could allow them to access or modify sensitive data. To fix this, update to n8n version 2.4.0 or later, or temporarily limit who can create workflows or disable the database nodes.
What to do
- Update GitHub Actions n8n to version 2.4.0.
Affected software
| Vendor | Product | Affected versions | Fix available |
|---|---|---|---|
| GitHub Actions | n8n | <= 2.4.0 | 2.4.0 |
Original title
n8n: SQL Injection in MySQL, PostgreSQL, and Microsoft SQL nodes
Original description
## Impact
An authenticated user with permission to create or modify workflows and access to a database credential could unknowingly create a workflow that was vulnerable to SQL injection, even while expecting inputs to be handled safely through escaped parameters. By supplying specially crafted table or column names, an attacker could inject arbitrary SQL because the MySQL, PostgreSQL, and Microsoft SQL nodes did not escape identifier values when constructing queries, enabling injection through node configuration parameters.
## Patches
The issue has been fixed in n8n version 2.4.0. Users should upgrade to this version or later to remediate the vulnerability.
## Workarounds
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 MySQL, PostgreSQL, and Microsoft SQL nodes by adding `n8n-nodes-base.mySql`, `n8n-nodes-base.postgres`, and `n8n-nodes-base.microsoftSql` to the `NODES_EXCLUDE` environment variable.
These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
## Credit
Reporter: Pawel Bednarz from the NATO Cyber Security Centre (NCSC)
An authenticated user with permission to create or modify workflows and access to a database credential could unknowingly create a workflow that was vulnerable to SQL injection, even while expecting inputs to be handled safely through escaped parameters. By supplying specially crafted table or column names, an attacker could inject arbitrary SQL because the MySQL, PostgreSQL, and Microsoft SQL nodes did not escape identifier values when constructing queries, enabling injection through node configuration parameters.
## Patches
The issue has been fixed in n8n version 2.4.0. Users should upgrade to this version or later to remediate the vulnerability.
## Workarounds
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 MySQL, PostgreSQL, and Microsoft SQL nodes by adding `n8n-nodes-base.mySql`, `n8n-nodes-base.postgres`, and `n8n-nodes-base.microsoftSql` to the `NODES_EXCLUDE` environment variable.
These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
## Credit
Reporter: Pawel Bednarz from the NATO Cyber Security Centre (NCSC)
ghsa CVSS3.1
8.2
ghsa CVSS4.0
5.3
Vulnerability type
CWE-89
SQL Injection
Published: 26 Feb 2026 · Updated: 7 Mar 2026 · First seen: 6 Mar 2026