Summary
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.
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.
Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access. Typical impact: data disclosure or modification.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
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.
Frequently Asked Questions
- What is CVE-2026-44792? CVE-2026-44792 is a high-severity SQL injection vulnerability in n8n (npm), affecting versions < 1.123.43. It is fixed in 1.123.43, 2.21.1, 2.20.7. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
- Which versions of n8n are affected by CVE-2026-44792? n8n (npm) versions < 1.123.43 is affected.
- Is there a fix for CVE-2026-44792? Yes. CVE-2026-44792 is fixed in 1.123.43, 2.21.1, 2.20.7. Upgrade to this version or later.
- Is CVE-2026-44792 exploitable, and should I be worried? Whether CVE-2026-44792 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-44792 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-44792?
- Upgrade
n8nto 1.123.43 or later - Upgrade
n8nto 2.21.1 or later - Upgrade
n8nto 2.20.7 or later
- Upgrade