dbcve.org
N8nApplication

CVE-2026-59257

HIGH · 8.8 CVSS v3.1 Published 2026-07-08
Fix available
A fix is available. Upgrade to 1.123.61 / 2.27.4 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click 6 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 1.123.61, 2.x before 2.27.4, and 2.28.x before 2.28.1 contains a SQL injection vulnerability in the legacy MySQL v1 node's executeQuery operation. The operation substitutes evaluated {{ ... }} expression values directly into the raw SQL string without parameterization. When a workflow uses this operation with expression-sourced values and is connected to an externally-reachable trigger (such as a Webhook node), attacker-controlled input reaching those expressions results in SQL injection, allowing execution of arbitrary SQL with the configured MySQL credentials' privileges. The MySQL v2 node, which uses parameterized queries, is not affected.

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 legacy MySQL v1 node where the executeQuery operation directly interpolates expression-sourced {{ ... }} values into raw SQL strings without parameterization. When workflows using this operation have externally-reachable triggers (e.g., Webhooks), attacker-controlled input can be injected through expressions to execute arbitrary SQL with the configured MySQL user's privileges. The MySQL v2 node uses parameterized queries and is unaffected.

MitigationMigrate affected workflows from the legacy MySQL v1 node to the MySQL v2 node which implements parameterized queries, or implement strict input validation if continued use of MySQL v1 is required.

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:< 1.123.61>= 2.0.0, < 2.27.4= 2.28.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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Check your installed n8n version
    Run 'n8n --version' from command line, or check the version in the n8n UI footer, or inspect package.json in the n8n installation directory
    Affected if Version is less than 1.123.61, OR version is 2.0.0 or higher but less than 2.27.4, OR version equals 2.28.0 exactly
  2. Identify workflows using the legacy MySQL v1 node
    Search workflow JSON files or query the n8n API endpoint /workflows for nodes with type 'n8n-nodes-base.mySql' or 'mysql' (not 'mysql2')
    Affected if Any active workflow contains the MySQL v1 node type (non-MySQL v2)
  3. Verify if MySQL v1 workflows are exposed via external triggers
    Inspect workflows using the MySQL v1 node and check if they include a Webhook node, a Form Trigger, or are set to receive external requests via HTTP Request node
    Affected if The MySQL v1 workflow is triggered by a publicly accessible webhook, form submission, or HTTP endpoint that accepts attacker-supplied input

You are affected if your n8n version falls within the vulnerable ranges AND you have workflows using the legacy MySQL v1 node that are reachable via externally-accessible endpoints accepting user input.

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 1.123.61 / 2.27.4 or later
Fixed in 1.123.612.27.4
Interim mitigation

Migrate affected workflows from the legacy MySQL v1 node to the MySQL v2 node which implements parameterized queries, or implement strict input validation if continued use of MySQL v1 is required.

Recommended fix High confidence

n8n 1.123.61 (1.x branch), 2.27.4 (2.x branch), or 2.28.1 (2.28.x branch) depending on your current major version

  1. 1. Identify the currently installed n8n version by checking the n8n instance or Docker container.
  2. 2. For n8n version 1.x users: Upgrade to version 1.123.61 or later.
  3. 3. For n8n version 2.0.0 - 2.27.3 users: Upgrade to version 2.27.4 or later.
  4. 4. For n8n version 2.28.0 users: Upgrade to version 2.28.1 or later.
  5. 5. After upgrading, verify that workflows using the MySQL v1 node still function correctly.
  6. 6. As a longer-term mitigation, consider migrating workflows from the legacy MySQL v1 node to the MySQL v2 node which uses parameterized queries and is not affected by this vulnerability.

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

Fix this in N8n Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-59257 — 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-59257 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