dbcve.org
N8nApplication

CVE-2026-56351

CRITICAL · 9.6 CVSS v3.1 Published 2026-06-24
Fix available
A fix is available. Upgrade to 2.4.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL injection vulnerability in n8n's MySQL, PostgreSQL, and Microsoft SQL nodes allows authenticated users with workflow creation permissions to inject arbitrary SQL through unescaped table and column names in node configuration parameters. The flaw stems from failure to properly escape SQL identifiers before constructing queries, enabling attackers to escape the intended query context and execute unauthorized database commands.

MitigationUpgrade n8n to version 2.4.0 or later which implements proper SQL identifier escaping. Until the upgrade is completed, restrict workflow creation permissions to highly trusted users only and consider implementing additional network-level database access controls.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
N8nApplication
Affected:< 2.4.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify n8n version
    Check your installed n8n version by accessing the system info endpoint or checking the package.json file in the n8n installation directory
    Affected if The installed version is lower than 2.4.0
  2. Identify database node usage
    Review all workflows in your n8n instance and identify any that contain MySQL, PostgreSQL, or Microsoft SQL nodes
    Affected if Workflows exist that use these database nodes and the n8n version is below 2.4.0
  3. Inspect SQL node configuration
    Examine the configuration of MySQL, PostgreSQL, and Microsoft SQL nodes in your workflows, specifically looking at table name and column name parameters
    Affected if Any SQL node configurations contain table or column names that might not be properly escaped or parameterized
  4. Review user permissions
    Check the user roles and permissions in your n8n instance to identify users with workflow creation privileges
    Affected if Users with workflow creation permissions exist and database nodes with potentially unescaped identifiers are in use

Your environment is affected if n8n version is below 2.4.0 AND workflows containing MySQL, PostgreSQL, or Microsoft SQL nodes with unescaped identifier parameters are active, especially when users with workflow creation permissions exist.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.4.0 or later
Fixed in 2.4.0
Interim mitigation

Upgrade n8n to version 2.4.0 or later which implements proper SQL identifier escaping. Until the upgrade is completed, restrict workflow creation permissions to highly trusted users only and consider implementing additional network-level database access controls.

Recommended fix High confidence

2.4.0

  1. Backup your current n8n installation and database before upgrading
  2. Check your current n8n version to confirm it is below 2.4.0
  3. Upgrade n8n to version 2.4.0 or later using your deployment method (npm, Docker, or binary)
  4. After upgrading, verify the new version is running (n8n --version or via UI)
  5. Confirm that MySQL, PostgreSQL, and Microsoft SQL nodes now properly escape identifier values in node configuration
  6. Test workflow execution with SQL nodes to ensure normal functionality is preserved

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in N8n Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-56351 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-56351 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data