---
id: GHSA-jqwr-vx3p-r266
title: >-
  n8n: PostgresTrigger Node SQL Injection Allows Authenticated Users to Execute
  Arbitrary SQL on Connected PostgreSQL Instances
summary: >-
  n8n: PostgresTrigger Node SQL Injection Allows Authenticated Users to Execute
  Arbitrary SQL on Connected PostgreSQL Instances
severity: medium
cwe:
  - CWE-89
vendor: n8n
product: n8n
ecosystem: npm
affected:
  - n8n < 1.123.67
  - 'n8n >= 2.32.0, < 2.32.1'
  - 'n8n >= 2.0.0-rc.0, < 2.31.5'
patched:
  - n8n 1.123.67
  - n8n 2.32.1
  - n8n 2.31.5
published: '2026-07-22'
updated: '2026-07-22'
source: GHSA
sourceUrl: 'https://github.com/advisories/GHSA-jqwr-vx3p-r266'
references:
  - url: 'https://github.com/n8n-io/n8n/security/advisories/GHSA-jqwr-vx3p-r266'
  - url: 'https://github.com/n8n-io/n8n/releases/tag/n8n@1.123.67'
  - url: 'https://github.com/n8n-io/n8n/releases/tag/n8n@2.31.5'
  - url: 'https://github.com/n8n-io/n8n/releases/tag/n8n@2.32.1'
  - url: 'https://github.com/advisories/GHSA-jqwr-vx3p-r266'
tags:
  - ghsa
  - npm
ingestedAt: '2026-07-23T00:08:38.556Z'
---

## Overview

## 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.

## Affected packages

- `n8n < 1.123.67`
- `n8n >= 2.32.0, < 2.32.1`
- `n8n >= 2.0.0-rc.0, < 2.31.5`

## Remediation

Upgrade to a patched release:

- `n8n 1.123.67`
- `n8n 2.32.1`
- `n8n 2.31.5`