| Component | n8n |
| Severity | high (CVSS 7) |
| CVSS vector | CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:H/SI:H/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| Published (NVD) | 2026-10-14 |
| Affected versions | < 2.41.4 >= 2.42.0, < 2.42.1 from the CVE Program record written by the CNA that assigned the CVE |
| Fixed in | 2.41.4, 2.42.1 |
| Weakness | CWE-89 |
| CISA KEV | not listed |
NVD description
n8n before 2.41.4 and 2.42.x before 2.42.1 contains an SQL injection vulnerability in version 1 of the Microsoft SQL node, which substitutes Query field expression values directly into SQL text without parameterisation. When a workflow binds untrusted input such as webhook fields to the Query field, unauthenticated external callers can execute arbitrary SQL against the connected database with the stored credential's privileges.
What to do
- Upgrade n8n to the fixed release of the branch you run:
2.41.4or2.42.1, or later. - Do not expose the component's API or UI to the internet without authentication in front of it.
Sources
- NVD: CVE-2026-110840
- https://github.com/n8n-io/n8n/security/advisories/GHSA-5qpp-pqww-h7fp
- https://www.vulncheck.com/advisories/n8n-before-2.41.4-and-2.42.1-sql-injection-via-microsoft-sql-node-query-field