PatchSiren cyber security CVE debrief
CVE-2026-72775 n8n-io CVE debrief
AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-08-11T13:19:08.040Z and has not been modified since then. The CVE-2026-72775 SQL injection vulnerability exists in the PostgresTrigger node of n8n before 1.123.67, 2.31.5, and 2.32.1. Authenticated users can inject arbitrary SQL, potentially leading to full read and write access to the connected PostgreSQL database. This vulnerability has a CVSS score of 5.8 and is classified as MEDIUM severity. Users of n8n should prioritize patching to prevent potential SQL injection attacks. The evidence is based on official CVE and NVD records, as well as advisories from the vendor and Vulncheck.
- Vendor
- n8n-io
- Product
- n8n
- CVSS
- MEDIUM 5.8
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-08-11
- Original CVE updated
- 2026-08-31
- Advisory published
- 2026-08-11
- Advisory updated
- 2026-08-31
Who should care
Users of n8n before 1.123.67, 2.31.5, and 2.32.1 who have the PostgresTrigger node configured should be aware of this vulnerability. Additionally, administrators and security teams responsible for the security of n8n installations should prioritize patching to prevent potential SQL injection attacks.
Technical summary
The CVE-2026-72775 vulnerability exists in the PostgresTrigger node of n8n before 1.123.67, 2.31.5, and 2.32.1. 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. The vulnerability has a CVSS score of 5.8 and is classified as MEDIUM severity. This SQL injection vulnerability can be exploited by authenticated users with access to the PostgresTrigger node, potentially leading to unauthorized database access and modifications. To mitigate this vulnerability, users should patch n8n to version 1.123.67, 2.31.5, or 2.32.1, or later, and restrict access to the PostgresTrigger node to only necessary users.
Defensive priority
Authenticated users with access to the PostgresTrigger node in n8n before 1.123.67, 2.31.5, and 2.32.1 should prioritize patching due to the MEDIUM severity of this SQL injection vulnerability.
Recommended defensive actions
- Patch n8n to version 1.123.67, 2.31.5, or 2.32.1, or later
- Restrict access to the PostgresTrigger node to only necessary users
- Monitor database activity for suspicious queries
- Consider implementing additional security controls, such as a Web Application Firewall (WAF)
- Inventory and verify the version of n8n in use
Evidence notes
The CVE-2026-72775 SQL injection vulnerability exists in the PostgresTrigger node of n8n before 1.123.67, 2.31.5, and 2.32.1. Authenticated users can inject arbitrary SQL, potentially leading to full read and write access to the connected PostgreSQL database. Evidence is based on official CVE and NVD records, as well as advisories from the vendor and Vulncheck.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-72775 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-72775
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-72775 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-72775
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/n8n-io/n8n/security/advisories/GHSA-jqwr-vx3p-r266
-
Source reference
Unverified legacy reference
URL: https://www.vulncheck.com/advisories/n8n-before-sql-injection-via-postgrestrigger-node
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.