CVE-2025-61917
published 2026-02-04CVE-2025-61917: n8n is an open source workflow automation platform. From version 1.65.0 to before 1.114.3, the use of Buffer.allocUnsafe() and Buffer.allocUnsafeSlow() in the…
PriorityP345high7.7CVSS 3.1
AVNACLPRLUINSCCHINAN
EPSS
0.36%
28.3th percentile
n8n is an open source workflow automation platform. From version 1.65.0 to before 1.114.3, 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. This issue has been patched in version 1.114.3.
Affected
3 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| n8n-io | n8n | — | — |
| n8n | n8n | >= 1.65.0 < 1.114.3 | 1.114.3 |
| n8n | n8n | >= 1.65.0 < 1.114.3 | 1.114.3 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
n8n's Unsafe Buffer Allocation Allows In-Process Memory Disclosure in Task Runner
osv·2026-02-04
CVE-2025-61917 [HIGH] n8n's Unsafe Buffer Allocation Allows In-Process Memory Disclosure in Task Runner
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:
- 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 tas
GHSA
n8n's Unsafe Buffer Allocation Allows In-Process Memory Disclosure in Task Runner
ghsa·2026-02-04
CVE-2025-61917 [HIGH] CWE-200 n8n's Unsafe Buffer Allocation Allows In-Process Memory Disclosure in Task Runner
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:
- 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 tas
No detection rules found.
No public exploits indexed.
2026-02-04
Published