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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.7 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

EPSS

• CVE-2025-61917: 0.40% estimated exploitation activity in the next 30 days; percentile 34.25 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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 N8NRUNNERSENABLED=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. - Fixed in: 1.114.3 & 1.115.0 - Action: It is strongly recommended to upgrade to version ≥ 1.114.3 as soon as possible. Changes introduced in this patch include: - Routing all buffer allocations through Buffer.alloc (which…

Published by the source

4 Feb 2026, 17:48 UTC

Last modified by the source

4 Feb 2026, 20:08 UTC

Source last checked

26 Oct 2026, 12:42 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-49mx-fj45-q3p6

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-49mx-fj45-q3p6

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-61917

Advisory: n8n's Unsafe Buffer Allocation Allows In-Process Memory Disclosure in Task Runner
IDs: CVE-2025-61917, GHSA-49mx-fj45-q3p6
Record: https://patchnext.com/advisories/cve-2025-61917 (revision 2, source checked 26 Oct 2026, 12:42 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: n8n 1.114.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm n8n: affected >= 1.65.0, < 1.114.3; fixed in 1.114.3

## Suggested inspection (read-only)
- `npm ls n8n --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on n8n.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-49mx-fj45-q3p6 (OSV record GHSA-49mx-fj45-q3p6 lists affected ranges: npm n8n >=1.65.0 <1.114.3 (fixed))
- Verified: https://github.com/advisories/GHSA-49mx-fj45-q3p6 (GitHub-reviewed advisory GHSA-49mx-fj45-q3p6 lists affected ranges: npm n8n >=1.65.0 <1.114.3)

Commands are suggestions: review each one before running it.