CVE-2026-44792: n8n: Source Control Pull SQL Injection
Impact An attacker with write access to the git repository connected to an n8n Source Control configuration could commit a malicious Data Table JSON file containing a crafted column name. When an administrator performed a Source Control Pull, n8n imported the file and could lead to SQL injection on the internal PostgreSQL instance.
Exploitation requires all of the following conditions: - The n8n instance uses PostgreSQL as its database backend. - The Source Control feature is enabled and connected to a repository the attacker can write to. - An administrator triggers a Source Control Pull.
Patches The issue has been fixed in n8n version 1.123.43, 2.20.7, and 2.21.1. Users should upgrade to this version or later to remediate the vulnerability.
Workarounds If upgrading is not immediately possible, administrators should consider the following temporary mitigations: - Disable the Source Control feature if it is not actively required. - Restrict write access to the connected git repository to fully trusted users only. - Avoid pulling from repositories that may have been modified by untrusted parties.
These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
Other sources
n8n is an open source workflow automation platform. Prior to 1.123.43, 2.22.1, and 2.20.7, an attacker with write access to the git repository connected to an n8n Source Control configuration could commit a malicious Data Table JSON file containing a crafted column name. When an administrator performed a Source Control Pull, n8n imported the file and could lead to SQL injection on the internal PostgreSQL instance. Exploitation requires the n8n instance uses PostgreSQL as its database backend, the Source Control feature is enabled and connected to a repository the attacker can write to, and an administrator triggers a Source Control Pull. This vulnerability is fixed in 1.123.43, 2.22.1, and 2.20.7.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
npm/n8nto a version that resolves this vulnerability.Fixed in 2.20.7 - Upgrade
Upgrade
npm/n8nto a version that resolves this vulnerability.Fixed in 2.21.1 - Upgrade
Upgrade
npm/n8nto a version that resolves this vulnerability.Fixed in 1.123.43 - Upgrade
Upgrade
npm/n8nto a version that resolves this vulnerability.Fixed in 2.22.1 - Configuration
Disable the Source Control feature if it is not actively required.
n8n Source Control feature enabled = false - Configuration
Restrict write access to the connected git repository to fully trusted users only.
Connected git repository write access = trusted users only - Compensating control
Avoid performing Source Control Pulls from repositories that may have been modified by untrusted parties; do not trigger pulls against repositories that are writable by untrusted users.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-44792?
CVE-2026-44792 has been classified as a high severity vulnerability due to the potential for SQL injection attacks.
How do I fix CVE-2026-44792?
To fix CVE-2026-44792, upgrade n8n to version 2.20.7, 2.21.1, or any version above 1.123.43.
What causes CVE-2026-44792?
CVE-2026-44792 is caused by an attacker exploiting write access to the git repository used with n8n's Source Control configuration.
Who is affected by CVE-2026-44792?
Users of n8n versions between 2.0.0-rc.0 and 2.20.7, as well as those below 1.123.43, are affected by CVE-2026-44792.
What type of attack can CVE-2026-44792 facilitate?
CVE-2026-44792 can facilitate SQL injection attacks when a malicious Data Table JSON file is imported.