CVE-2026-49444·Python vulnerability
n8n is an open source workflow automation platform. Prior to 1.123.48, 2.21.8, and 2.22.4, an authenticated user with permission to create or modify workflows containing a Python Code Node could escape the sandbox and achieve arbitrary code execution on the task runner container. This vulnerability is fixed in 1.123.48, 2.21.8, and 2.22.4.
- Severity
- high
- Software
- Python
- Fixed in
- 2.22.4
- Published
- 2026-06-23
Affected versions
From: 2.22.0
Until: 2.22.4
Fixed in: 2.22.4
How to fix this CVE
Update n8n immediately to version 2.22.4 or later to patch the Python Code Node sandbox escape vulnerability. Authenticated users with workflow modification permissions could previously bypass sandbox protections and execute arbitrary code on the task runner. Verify the patched version is running and audit recent workflow modifications for suspicious Python code nodes.
sudo dnf update python3Defensia detects this vulnerability
How to check if you are affected
- Run `python3 --version` to check the installed Python version on your n8n task runner container
- Verify n8n version with `npm list n8n` or check the version file in your n8n installation directory
- Search n8n workflow execution logs for Python Code Node executions using commands like: `grep -r 'pythonCode\|execCode' /path/to/n8n/logs/`
- Confirm the patch was applied by verifying n8n version >= 2.22.4 with `npm info n8n | grep latest`
FAQ
What is CVE-2026-49444?
This vulnerability affects n8n's Python Code Node, allowing authenticated users with workflow creation/modification permissions to break out of the sandbox environment and run arbitrary code directly on the container running task execution. The vulnerability exists in versions prior to 2.22.4.
Is CVE-2026-49444 being actively exploited?
No, this vulnerability is not currently listed on CISA's Known Exploited Vulnerabilities (KEV) catalog and no public exploit code has been released. However, the attack requires only authenticated access, making insider threats a significant concern.
What versions of n8n are affected by CVE-2026-49444?
n8n versions 2.22.0 through 2.22.3 are vulnerable. Version 2.22.4 and later contain the fix. Users on earlier major versions (1.x and 2.21.x) should also upgrade to 1.123.48 or 2.21.8 respectively.
How do I check if my server is vulnerable to CVE-2026-49444?
Run `npm list n8n` to check your installed version. If the version is between 2.22.0 and 2.22.3, your installation is vulnerable. Compare output against the fixed versions: 1.123.48, 2.21.8, or 2.22.4.
Does Defensia detect CVE-2026-49444?
Yes — Defensia's CVE advisory scanner compares installed n8n package versions against the NVD database and security advisories. If a vulnerable version is detected on your monitored infrastructure, CVE-2026-49444 will appear in your dashboard with specific remediation commands and risk assessment.
Related Python CVEs
References
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-49444. Free for 1 server.
Get started free