GHSA-xvh5-5qg4-x9qp: n8n has In-Process Memory Disclosure in its Task Runner

Summary

An authenticated user with permission to create or modify workflows can use the JavaScript Task Runner in n8n to allocate uninitialized memory buffers. Those buffers may contain residual data from the same Node.js process, including prior requests, tasks, secrets, or tokens, when Task Runners are enabled with N8N_RUNNERS_ENABLED=true. In external runner mode, exposure is limited to the external runner process.

Mitigation

The issue is fixed in n8n versions >= 1.123.22, >= 2.10.1, and >= 2.9.3; users should upgrade to these or later. If upgrading is not immediately possible, limit workflow creation and editing permissions to fully trusted users only, or use external runner mode (N8N_RUNNERS_MODE=external) to isolate the runner process. These workarounds do not fully remediate the risk and are short-term measures only.

Affected packages in the Exposure Registry

Matched by package name and ecosystem. Each entry shows whether the package delegates to a language model and how many tracked packages depend on it.

• n8nnpmLLM dependency since 2026-02-10

Related items

• HighCVE-2026-123818: LMDeploy is a toolkit for compressing, deploying, and serving large language models. From 0.12.3 until 0.15.0…Similar attack · NVD/CVE Database
• HighGHSA-vvr2-h2jp-838m: Code Graph RAG: MCP paginated read_file path traversal / arbitrary file readSimilar attack · GitHub Advisory Database
• MediumAttackers Crash Claude's 'Office Party' Flaw to Run Malicious Code on LinuxSimilar attack · Dark Reading
• MediumCVE-2026-124588: huggingface finetrainers code injection via Library argumentSimilar attack · NVD/CVE Database
• MediumTaiwan-Based Hacker Used BOSSAI AI Agents to Steal Taipei Emergency Dispatch RecordsSimilar attack · The Hacker News