CVE-2026-72775
Received Received - Intake

SQL Injection in n8n PostgresTrigger Node

Publication date: 2026-08-11

Last updated on: 2026-08-11

Assigner: VulnCheck

Description
n8n before 1.123.67, 2.31.5, and 2.32.1 contains a SQL injection vulnerability in the PostgresTrigger node, which interpolates user-supplied identifier parameters (channel, function, and trigger names) into SQL statements without proper escaping. An authenticated user can inject arbitrary SQL executed against the connected PostgreSQL database with the configured credential's privileges, allowing full read and write access.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-11
Last Modified
2026-08-11
Generated
2026-08-11
AI Q&A
2026-08-11
EPSS Evaluated
N/A
NVD
CVE-2026-72775
EUVD
EUVD-2026-56101

Affected Vendors & Products

Showing 5 associated CPEs
Vendor Product Version / Range
n8n n8n to 1.123.67 (exc)
n8n n8n 2.31.5
n8n n8n 2.32.1
n8n n8n to 1.123.67|end_excluding=2.31.5|end_excluding=2.32.1 (exc)
n8n n8n 1.123.67

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a SQL injection vulnerability in the n8n workflow automation tool, specifically in the PostgresTrigger node. It allows authenticated users to inject arbitrary SQL commands into the connected PostgreSQL database without proper input sanitization. The flaw occurs because user-supplied parameters like channel, function, and trigger names are directly interpolated into SQL statements.

Detection Guidance

To detect this vulnerability, check if your n8n instance uses versions before 1.123.67, 2.31.5, or 2.32.1. Inspect the PostgresTrigger node configurations for suspicious SQL patterns in logs. Monitor PostgreSQL database activity for unauthorized queries or unexpected data access.

Impact Analysis

An attacker with authenticated access can execute arbitrary SQL commands, gaining full read and write access to the PostgreSQL database. This could lead to data theft, unauthorized modifications, or database corruption. The impact depends on the database's configured privileges and the sensitivity of the stored data.

Compliance Impact

This vulnerability can severely impact compliance with GDPR and HIPAA by enabling unauthorized access to sensitive personal or health data. It may result in data breaches, violating confidentiality requirements and leading to legal penalties, fines, or reputational damage for organizations handling regulated data.

Mitigation Strategies

Upgrade n8n to versions 1.123.67, 2.31.5, or 2.32.1 or later. Disable the PostgresTrigger node if not needed. Restrict access to n8n to trusted users only. Ensure PostgreSQL credentials have minimal required privileges.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-72775. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart