dbcve.org
N8nApplication

CVE-2026-54310

CRITICAL · 9.9 CVSS v3.1 Published 2026-06-23
Fix available
A fix is available. Upgrade to 2.25.7 / 2.26.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 is an open source workflow automation platform. Prior to 2.25.7 and 2.26.2, an authenticated user with permission to create or modify workflows could supply a crafted parameters to the TimescaleDB and/or legacy Postgres v1 node's allowing arbitrary SQL to be injected and executed against the connected database within the privileges of the configured database account. This vulnerability is fixed in 2.25.7 and 2.26.2.

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 TimescaleDB and legacy Postgres v1 nodes allows authenticated users with workflow creation/modification permissions to inject and execute arbitrary SQL queries against the connected database, limited only by the database account's privileges.

MitigationUpgrade n8n to version 2.25.7 or 2.26.2 or later. Until then, restrict workflow permissions to trusted users only and review database account privileges.

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.25.7>= 2.26.0, < 2.26.2

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
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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. Determine installed n8n version
    Run 'n8n --version' from command line, check the Docker container tag, or look in package.json if self-hosted
    Affected if Version is < 2.25.7 OR (>= 2.26.0 AND < 2.26.2)
  2. Identify TimescaleDB or Postgres v1 nodes in workflows
    In n8n UI, open each workflow and inspect node list for 'TimescaleDB' or 'Postgres v1' node types; or query the workflow database table for node types containing 'postgres' or 'timescale'
    Affected if Workflows contain TimescaleDB or Postgres v1 nodes
  3. Check if workflow creation/modification permissions are enabled
    In n8n UI, go to Users/Permissions settings and review which users or roles have 'workflow create' or 'workflow update' permissions enabled
    Affected if More than one user or untrusted users have workflow creation or modification permissions
  4. Review connected database account privileges
    Examine the database credentials used in TimescaleDB/Postgres v1 node connection settings, then check what privileges that database user has (e.g., SELECT, INSERT, UPDATE, DELETE, or DDL permissions)
    Affected if The database account has broader privileges than strictly required for the workflow's data operations

User is affected if n8n version falls within the vulnerable range AND TimescaleDB/Postgres v1 nodes are in use with workflow creation/modification permissions enabled for the querying user.

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.25.7 / 2.26.2 or later
Fixed in 2.25.72.26.2
Interim mitigation

Upgrade n8n to version 2.25.7 or 2.26.2 or later. Until then, restrict workflow permissions to trusted users only and review database account privileges.

Recommended fix High confidence

n8n version 2.25.7 or 2.26.2 (depending on your current branch)

  1. Identify the current n8n version running in your environment
  2. If current version is < 2.25.7, upgrade to version 2.25.7
  3. If current version is >= 2.26.0 and < 2.26.2, upgrade to version 2.26.2
  4. Verify the upgrade was successful by checking the n8n version
  5. If using TimescaleDB or legacy Postgres v1 nodes, review the database account permissions to follow principle of least privilege
Caveat Review n8n release notes for version 2.25.7 and 2.26.2 to check for any breaking changes in your workflow configurations

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

Fix this in N8n Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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