https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 15 Oct 2026 03:05:06 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-329777 EUVD-2026-329777 https://cve.radiocsirt.org/vuln/euvd-2026-329777 https://cve.radiocsirt.org/vuln/fkie_cve-2026-56351 <p>n8n before version 2.4.0 contains a sql injection vulnerability in MySQL, PostgreSQL, and Microsoft SQL nodes that allows authenticated users to inject arbitrary SQL through unescaped identifier values in node configuration parameters. Attackers with workflow creation permissions can supply specially crafted table or column names to execute unauthorized database commands and compromise data integrity.</p> <p>n8n before version 2.4.0 contains a sql injection vulnerability in MySQL, PostgreSQL, and Microsoft SQL nodes that allows authenticated users to inject arbitrary SQL through unescaped identifier values in node configuration parameters. Attackers with workflow creation permissions can supply specially crafted table or column names to execute unauthorized database commands and compromise data integrity.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-56351 https://cve.radiocsirt.org/vuln/ghsa-f3f2-mcxc-pwjx <p><strong>Affected:</strong> npm: n8n</p> <p>## 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.</p> <p>## Patches The issue has been fixed in n8n version 2.4.0. Users should upgrade to this version or later to remediate the vulnerability.</p> <p>## 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.</p> <p>These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.</p> <p>## Credit</p> <p>Reporter: Pawel Bednarz from the NATO Cyber Security Centre (NCSC)</p> <p><strong>Affected:</strong> npm: n8n</p> <p>## 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.</p> <p>## Patches The issue has been fixed in n8n version 2.4.0. Users should upgrade to this version or later to remediate the vulnerability.</p> <p>## 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.</p> <p>These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.</p> <p>## Credit</p> <p>Reporter: Pawel Bednarz from the NATO Cyber Security Centre (NCSC)</p> https://cve.radiocsirt.org/vuln/ghsa-f3f2-mcxc-pwjx