Vulnerability · Published Feb 4, 2026 · Assigned by GitHub_M

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

High 7.7

In plain English

A high-severity information exposure in n8n from n8n-io. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.4% (higher than 34% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)7.7High

Exploit odds (30 days)0.4%top 66.0% of all CVEs

Exploited in the wildNo reportsCISA SSVC: none

Attack toolingNoneno public tooling known

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.

Affected packages & fixed versions

Ecosystem	Package	Fixed in	Advisory
npm	n8n	1.114.3	GHSA-49mx-fj45-q3p6

Affected products (as reported)

Vendor	Product	Versions
n8n-io	n8n	>= 1.65.0, < 1.114.3

Weakness: CWE-668, CWE-200 · Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

References

https://github.com/n8n-io/n8n/security/advisories/GHSA-49mx-fj45-q3p6 x_refsource_CONFIRM
https://github.com/n8n-io/n8n/commit/2c4c2953199733c791f739a40879ae31ca129aba x_refsource_MISC