CVE-2025-61917 n8n Unsafe Buffer Allocation Allows In-Process Memory Disclosure in Task Runner

High 7.7 Published Updated

Untrusted code in n8n task runner can access uninitialized memory, potentially exposing secrets and tokens from the same process.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2025-61917?

CVE-2025-61917 is a high-severity vulnerability in N8n N8n, published on 4 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

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.

Weakness: CWE-668, CWE-200

Which versions are affected by CVE-2025-61917?

2 open source packages ship an affected version, including n8n. It affects 1 product.

PackageAffectedFixed in
n8n npmFrom 1.65.01.114.3
n8n npmFrom 1.65.01.114.3

Products include N8n N8n.

How do I fix CVE-2025-61917?

Upgrade n8n to 1.114.3 or later.

Is CVE-2025-61917 being exploited?

There is no known exploitation of CVE-2025-61917 in the wild and no public exploit code.

All N8n N8n vulnerabilities

Sources

Also known as GHSA-49mx-fj45-q3p6.

Is CVE-2025-61917 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free