Advisory

GHSA-xvh5-5qg4-x9qp

Also known as: CVE-2026-27496

Summary

n8n has In-Process Memory Disclosure in its Task Runner

Details

Impact
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.

Patches
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.

Workarounds
If upgrading is not immediately possible, administrators should consider the following temporary mitigations:

  • Limit workflow creation and editing permissions to fully trusted users only.
  • 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.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2026-03-25 17:00 UTC
Modified
2026-03-27 22:17 UTC

Affected packages and fixes

n8n

npm · All systems

Affected

  • introduced 0, fixed 1.123.22 (semver)

Fixed versions

1.123.22

Fix

n8n

npm · All systems

Affected

  • introduced 2.10.0, fixed 2.10.1 (semver)

Fixed versions

2.10.1

Fix

n8n

npm · All systems

Affected

  • introduced 2.0.0-rc.0, fixed 2.9.3 (semver)

Fixed versions

2.9.3

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences