AI agent vulnerability · n8n

GHSA-jqwr-vx3p-r266: n8n: PostgresTrigger Node SQL Injection Allows Authenticated Users to Execute Arbitrary SQL on Connected PostgreSQL Instances

mediumCVSS 4.0 5.8

Impact The Postgres Trigger node interpolated user-supplied identifier parameters (channel, function, and trigger names) into SQL statements without proper escaping, so an authenticated user could inject arbitrary SQL executed against the connected PostgreSQL database with the configured credential's privileges. Successful exploitation allows full read and write access to the connected PostgreSQL database.

Published Jul 22, 2026

Affected packages

n8n

Ecosystem: npm
Affected: < 1.123.67
Fixed in: 1.123.67
Check: npm ls n8n

n8n

Ecosystem: npm
Affected: >= 2.32.0, < 2.32.1
Fixed in: 2.32.1
Check: npm ls n8n

n8n

Ecosystem: npm
Affected: >= 2.0.0-rc.0, < 2.31.5
Fixed in: 2.31.5
Check: npm ls n8n

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

Impact

The Postgres Trigger node interpolated user-supplied identifier parameters (channel, function, and trigger names) into SQL statements without proper escaping, so an authenticated user could inject arbitrary SQL executed against the connected PostgreSQL database with the configured credential's privileges.

Successful exploitation allows full read and write access to the connected PostgreSQL database.

Patches

The issue has been fixed in n8n versions 1.123.67, 2.31.5 and 2.32.1. Users should upgrade to these versions or later to remediate the vulnerability.

Workarounds

If upgrading is not immediately possible, administrators should consider the following temporary mitigations:

Restrict n8n instance access to fully trusted users only.
Disable the PostgresTrigger node by adding n8n-nodes-base.postgresTrigger to the NODES_EXCLUDE environment variable.
Ensure PostgreSQL credentials used with n8n are configured with the minimum required privileges and do not use SUPERUSER roles.

These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

Credited to sm1ee.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More n8n vulnerabilities

All n8n entries