Which versions of PostgreSQL are affected by CVE-2026-33713?

A SQL injection vulnerability in n8n's Data Table Get node allows authenticated workflow users to manipulate database queries, posing a critical risk to organizations using PostgreSQL backends where…. A patch is available.

Is there a public PoC exploit available for CVE-2026-33713?

Yes, a public proof-of-concept exploit is available for CVE-2026-33713. Prioritise patching immediately. EPSS: 0.0%.

How to fix or mitigate CVE-2026-33713?

Within 24 hours: Identify all n8n instances in your environment and determine which use PostgreSQL versus SQLite backends; restrict workflow creation/modification permissions to essential personnel only. Within 7 days: Implement network segmentation to limit n8n database access, disable the Data Table Get node if unused, and apply input validation/WAF rules to detect SQL injection patterns in workflow definitions. Within 30 days: Monitor vendor communications for patch availability and establish a deployment plan; conduct a review of all existing workflows using Data Table Get nodes for potential compromise.

PostgreSQL CVE-2026-33713

Q: What is the CVSS score of CVE-2026-33713?

CVE-2026-33713 has a CVSS 4.0 base score of 8.7 (High). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.0%.

EUVD-2026-15947 HIGH

SQL Injection (CWE-89)

2026-03-25 GitHub_M

GHSA-98c2-4cr3-4jc3

SQLi PostgreSQL N8n N8N Io

8.7

CVSS 4.0 · GitHub Advisory

Severity by source

GitHub Advisory PRIMARY

8.7 HIGH

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Patch released

Mar 31, 2026 - 21:13 nvd

Patch available

PoC Detected

Mar 27, 2026 - 19:39 vuln.today

Public exploit code

EUVD ID Assigned

Mar 25, 2026 - 18:01 euvd

EUVD-2026-15947

Analysis Generated

Mar 25, 2026 - 18:01 vuln.today

CVE Published

Mar 25, 2026 - 17:47 nvd

HIGH 8.7

DescriptionGitHub Advisory

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.

AnalysisAI

SQL injection in n8n's Data Table Get node allows authenticated users with workflow modification permissions to execute arbitrary SQL queries against PostgreSQL backends, enabling data modification and deletion. Public exploit code exists for this vulnerability. Affected versions prior to 1.123.26, 2.13.3, and 2.14.1 should be upgraded immediately, or workflow creation/editing permissions should be restricted to trusted users only.

Technical ContextAI

The vulnerability affects n8n workflow automation platform (cpe:2.3:a:n8n-io:n8n) and is rooted in CWE-89 (SQL Injection). The Data Table Get node's orderByColumn parameter fails to properly sanitize user-supplied input when it incorporates expressions or external data, allowing SQL code injection into database queries. The technical impact varies significantly by database backend: SQLite's single-statement execution model inherently limits exploitation surface, while PostgreSQL's multi-statement capabilities enable stacked queries that can perform arbitrary data manipulation operations including INSERT, UPDATE, DELETE, and potentially privilege escalation through database-specific functions. This differential impact highlights how the underlying database technology directly influences exploitability severity.

RemediationAI

Upgrade n8n to version 1.123.26, 2.13.3, 2.14.1 or later depending on your current version branch to fully remediate this vulnerability (see GitHub advisory at https://github.com/n8n-io/n8n/security/advisories/GHSA-98c2-4cr3-4jc3). If immediate patching is not feasible, implement temporary mitigations including restricting workflow creation and editing permissions exclusively to fully trusted users, disabling the Data Table node by adding n8n-nodes-base.dataTable to the NODES_EXCLUDE environment variable, and auditing existing workflows to identify Data Table Get nodes where orderByColumn uses expressions incorporating external or user-supplied input. Note that these workarounds provide only partial risk reduction and should be considered short-term measures until proper patching can be completed.