n8n
Affected
- introduced
1.65.0, fixed1.114.3(semver)
Fixed versions
1.114.3
Fix
- Fixed version
1.114.3npm install [email protected]
Advisory
Also known as: CVE-2025-61917
n8n's Unsafe Buffer Allocation Allows In-Process Memory Disclosure in Task Runner
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:
N8N_RUNNERS_ENABLED=true (default: false)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:
Buffer.alloc (which zero-fills) operations where applicable Workarounds
If an immediate upgrade cannot be applied, the following hardening steps are recommended:
n8n-nodes-base.code to the NODES_EXCLUDE environment variable Resources
High Basis: The source's own band: HIGH
1.65.0, fixed 1.114.3 (semver)1.114.3
1.114.3npm install [email protected]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
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0