dbcve.org
N8nApplication

CVE-2026-33713

HIGH · 8.8 CVSS v3.1 Published 2026-03-25
Fix available
A fix is available. Upgrade to 1.123.26 / 2.13.3 or later.
See remediation →
94/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 versions 2.14.1, 2.13.3, and 1.123.26, an authenticated user with permission to create or modify workflows could exploit a SQL injection vulnerability in the Data Table Get node. On default SQLite DB, single statements can be manipulated and the attack surface is practically limited. On PostgreSQL deployments, multi-statement execution is possible, enabling data modification and deletion. The issue has been fixed in n8n versions 1.123.26, 2.13.3, and 2.14.1. Users should upgrade to one of these versions or later to remediate the vulnerability. 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 Data Table node by adding `n8n-nodes-base.dataTable` to the `NODES_EXCLUDE` environment variable, and/or review existing workflows for Data Table Get nodes where `orderByColumn` is set to an expression that incorporates external or user-supplied input. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

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 Data Table Get node allows authenticated users with workflow modification permissions to inject malicious SQL via the orderByColumn parameter. On PostgreSQL deployments, multi-statement execution enables data exfiltration, modification, or deletion. SQLite is limited to single-statement manipulation.

MitigationUpgrade immediately to n8n versions 1.123.26, 2.13.3, or 2.14.1 or later. As temporary measures, limit workflow permissions to trusted users, disable the Data Table node via NODES_EXCLUDE environment variable, and audit existing workflows for vulnerable configurations.

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.26>= 2.0.0, < 2.13.3= 2.14.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 installed n8n version
    Run `n8n --version` or check the version in the UI footer. On Docker, run `docker exec <container> n8n --version`. Compare against affected ranges: < 1.123.26, >= 2.0.0 and < 2.13.3, or exactly 2.14.0
    Affected if Version matches any affected range listed above
  2. Identify Data Table Get node usage
    Review all active workflows in the n8n UI or export workflows to search for nodes of type "n8n-nodes-base.dataTable" or specifically the "Data Table Get" node
    Affected if Any workflow uses the Data Table Get node
  3. Verify database backend type
    Check n8n configuration for DB_TYPE environment variable or inspect the database connection string. PostgreSQL enables multi-statement execution which allows more severe exploitation; SQLite is limited to single statements
    Affected if Database is PostgreSQL (more severe) or SQLite with the Data Table Get node in use
  4. Review user permission levels
    Check user roles and workflow permissions in n8n settings. Identify users with "workflow editor" or "workflow modifier" roles who can create or edit workflows
    Affected if Untrusted or external users have workflow modification permissions and Data Table Get node is in use

You are affected if your n8n version is vulnerable AND the Data Table Get node is used by someone with workflow modification permissions, with PostgreSQL deployments at highest risk.

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.26 / 2.13.3 or later
Fixed in 1.123.262.13.3
Interim mitigation

Upgrade immediately to n8n versions 1.123.26, 2.13.3, or 2.14.1 or later. As temporary measures, limit workflow permissions to trusted users, disable the Data Table node via NODES_EXCLUDE environment variable, and audit existing workflows for vulnerable configurations.

Recommended fix High confidence

1.123.26 (for v1.x) | 2.13.3 (for v2.x pre-2.13) | 2.14.1 (for v2.14.0)

  1. Identify your current n8n version by checking the UI or running `n8n --version`
  2. Backup your n8n database and any custom workflows before upgrading
  3. If using n8n version 1.x: Upgrade to version 1.123.26 or later
  4. If using n8n version 2.x (2.0.0 - 2.13.2): Upgrade to version 2.13.3 or later
  5. If using n8n version 2.14.0: Upgrade to version 2.14.1 or later
  6. Restart the n8n service after upgrading
  7. Verify the upgrade was successful by checking the n8n version and testing workflow functionality

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

Fix this in N8n Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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