Compliance Impact

This vulnerability allows an attacker to perform SQL injection on the internal PostgreSQL database of the n8n platform if certain conditions are met. Such an attack could lead to unauthorized access, modification, or disclosure of sensitive data stored within the database.

Unauthorized access or compromise of sensitive data can negatively impact compliance with common standards and regulations such as GDPR and HIPAA, which require protection of personal and health-related information against breaches and unauthorized access.

Therefore, if exploited, this vulnerability could result in violations of data protection requirements mandated by these regulations, potentially leading to legal and financial consequences for affected organizations.

Useful 0 Not Useful 0

Executive Summary

CVE-2026-44792 is a high-severity SQL injection vulnerability in the n8n workflow automation platform versions prior to 1.123.43, 2.20.7, and 2.21.1.

The vulnerability occurs when an attacker who has write access to a git repository connected to n8n's Source Control feature commits a malicious Data Table JSON file containing a specially crafted column name.

When an administrator performs a Source Control Pull, n8n imports this malicious file, which can lead to SQL injection attacks on the internal PostgreSQL database used by n8n.

Exploitation requires that the n8n instance uses PostgreSQL as its database backend, the Source Control feature is enabled and connected to a repository writable by the attacker, and an administrator triggers the pull.

The issue has been fixed in versions 1.123.43, 2.22.1, and 2.20.7.

Useful 0 Not Useful 0

Impact Analysis

This vulnerability can allow an attacker to perform SQL injection on the internal PostgreSQL database of the n8n instance.

Successful exploitation could lead to unauthorized data access, data manipulation, or corruption within the database.

Because the attack requires write access to the connected git repository and an administrator to trigger a Source Control Pull, the risk is elevated in environments where repository access controls are weak or administrative actions are not carefully managed.

Temporary mitigations include disabling the Source Control feature, restricting write access to the repository, or avoiding pulls from untrusted repositories, but these do not fully eliminate the risk.

Useful 0 Not Useful 0

Detection Guidance

Detection of this vulnerability involves verifying if your n8n instance is running a vulnerable version prior to 1.123.43, 2.20.7, or 2.21.1, and if the Source Control feature is enabled and connected to a git repository with write access.

You can check the n8n version by running the following command on the system hosting n8n:

• n8n --version

To verify if Source Control is enabled and configured, inspect the n8n configuration or environment variables related to Source Control settings.

Additionally, review the connected git repository permissions to confirm if untrusted users have write access.

There are no specific network detection commands or signatures provided for this vulnerability.

Useful 0 Not Useful 0

Mitigation Strategies

Immediate mitigation steps include:

• Upgrade n8n to version 1.123.43, 2.22.1, or 2.20.7 or later, where the vulnerability is fixed.
• Disable the Source Control feature temporarily to prevent importing potentially malicious Data Table JSON files.
• Restrict write access to the connected git repository to trusted users only.
• Avoid performing Source Control Pull operations from untrusted or potentially compromised repositories.

Useful 0 Not Useful 0