n8n: SQL Injection in MySQL, PostgreSQL, and Microsoft SQL nodes

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

5.3 · CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N · score source

EPSS

• CVE-2026-56351: 0.38% estimated exploitation activity in the next 30 days; percentile 31.56 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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…

Published by the source

26 Feb 2026, 15:56 UTC

Last modified by the source

20 Jul 2026, 21:46 UTC

Source last checked

26 Oct 2026, 12:57 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-f3f2-mcxc-pwjx

2. Revision 2 · amended · 24 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-f3f2-mcxc-pwjx

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-56351

Advisory: n8n: SQL Injection in MySQL, PostgreSQL, and Microsoft SQL nodes
IDs: CVE-2026-56351, GHSA-f3f2-mcxc-pwjx
Record: https://patchnext.com/advisories/cve-2026-56351 (revision 3, source checked 26 Oct 2026, 12:57 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: n8n 2.4.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm n8n: affected < 2.4.0; fixed in 2.4.0

## Suggested inspection (read-only)
- `npm ls n8n --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on n8n.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-f3f2-mcxc-pwjx (OSV record GHSA-f3f2-mcxc-pwjx lists affected ranges: npm n8n >=0 <2.4.0 (fixed))
- Verified: https://github.com/advisories/GHSA-f3f2-mcxc-pwjx (GitHub-reviewed advisory GHSA-f3f2-mcxc-pwjx lists affected ranges: npm n8n >=0 <2.4.0)

Commands are suggestions: review each one before running it.