Quick answers
- Is CVE-2026-44792 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44792 being exploited in the wild.
- How severe is CVE-2026-44792?
- Critical severity, with a CVSS score of 9, published 23 June 2026.
- Which products and versions are affected?
- N8n < 1.123.43, < 2.21.1, < 2.20.7, < 1.123.43, >= 2.0.0-rc.0 < 2.20.7, >= 2.21.0 < 2.21.1, < 1.123.43, >= 2.0.0-rc.0, < 2.20.7, >= 2.21.0, < 2.21.1; n8n (npm) SEMVER:introduced=0,fixed=1.123.43.
- Is there a fix for CVE-2026-44792?
- Yes. n8n (npm): upgrade to 1.123.43 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-44792 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-44792?
- Check whether you run N8n or n8n (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- n8n (npm): upgrade to 1.123.43 or later
npm install n8n@1.123.43
Technical details
A SQL injection vulnerability exists in n8n's Source Control feature due to improper neutralization of special elements in Data Table JSON files. An attacker with write access to the connected Git repository can commit a crafted JSON file with a malicious column name. When an administrator triggers a 'Source Control Pull', the application imports the file and executes the injected SQL against the internal PostgreSQL backend. This requires the instance to be using PostgreSQL and the Source Control feature to be active. The issue is fixed in versions 1.123.43, 2.20.7, and 2.21.1.
Affected products
- n8n-io n8n < 1.123.43, >= 2.0.0-rc.0, < 2.20.7, >= 2.21.0, < 2.21.1
Identifiers
- CVE-2026-44792
- GHSA-mhrx-qhrj-673w
Timeline
- 2026-05-13: disclosed
- 2026-05-14: advisory