Vulnerability 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.
CVSS Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| N8N | N8N | >= 1.65.0, < 1.114.3 |
Related Weaknesses (CWE)
References
- https://github.com/n8n-io/n8n/commit/2c4c2953199733c791f739a40879ae31ca129abaPatch
- https://github.com/n8n-io/n8n/security/advisories/GHSA-49mx-fj45-q3p6MitigationVendor Advisory
FAQ
What is CVE-2025-61917?
CVE-2025-61917 is a vulnerability with a CVSS score of 7.7 (HIGH). 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 all...
How severe is CVE-2025-61917?
CVE-2025-61917 has been rated HIGH with a CVSS base score of 7.7/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2025-61917?
Check the references section above for vendor advisories and patch information. Affected products include: N8N N8N.