CVE-2026-72775GHSA-JQWR-VX3P-R266
n8n before 1.123.67 SQL Injection via PostgresTrigger Node
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.123.67, 2.32.1, 2.31.5
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- n8n-io n8n
fixed in 1.123.67
- n8n-io n8n
From 2.32.0 · fixed in 2.32.1
- n8n-io n8n
From 2.0.0-rc.0 · fixed in 2.31.5
- n8nnpm
fixed in 1.123.67
- n8nnpm
From 2.32.0 · fixed in 2.32.1
- n8nnpm
From 2.0.0-rc.0 · fixed in 2.31.5