MISFIRE

Browse / AI Framework and Platform Flaws / CVE-2025-61917

n8n's Unsafe Buffer Allocation Allows In-Process Memory Disclosure in Task Runner

CVE-2025-61917 · 2026-02-04 high

Class
AI Framework and Platform Flaws (filed by a model that read the source)
Technique
Information exposure
Affected
n8n (npm)
CVSS
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
EPSS
0.4% chance of exploitation in 30 days

How it works, in short

Untrusted task runner code can call unsafe buffer allocation and receive uninitialized memory that may hold residual data from the same process. (Our summary, written by a model. The source text is below.)

Details

Impact

The use of Buffer.allocUnsafe() and Buffer.allocUnsafeSlow() in the task runner allowed untrusted code to allocate uninitialized memory. Such uninitialized buffers could contain residual data from within the same Node.js process (for example, data from prior requests, tasks, secrets, or tokens), resulting in potential information disclosure.

Only authenticated users are able to execute code through Task Runners.

This issue affected any deployment in which both of the following conditions were met:
- Task Runners were enabled using N8N_RUNNERS_ENABLED=true (default: false)
- Code Node was enabled (default: true)

Patches

Access to unsafe Buffer functions has been removed from the task runner sandbox. All buffer allocations are now zero-filled by default.

Changes introduced in this patch include:
- Routing all buffer allocations through Buffer.alloc (which zero-fills) operations where applicable
- Adding regression tests to ensure continued enforcement of safe allocation practices

Workarounds

If an immediate upgrade cannot be applied, the following hardening steps are recommended:

Resources

References

Source: GitHub Advisory Database, used under CC BY 4.0.