Authenticated memory disclosure via unsafe buffer allocation
Published Feb 4, 2026 · Updated Feb 4, 2026
Information disclosure in n8n 1.65.0 through 1.114.2 allows remote authenticated users to read residual process memory via task code. The JavaScript task runner exposed Buffer.allocUnsafe() and Buffer.allocUnsafeSlow() directly, returning uninitialized bytes rather than zero-filled buffers. Exploitation requires Task Runners enabled, the Code Node available, and permission to execute task code; disclosure is limited to residual data in the same Node.js process.
Summary
What happened
Information disclosure in n8n 1.65.0 through 1.114.2 allows remote authenticated users to read residual process memory via task code. The JavaScript task runner exposed Buffer.allocUnsafe() and Buffer.allocUnsafeSlow() directly, returning uninitialized bytes rather than zero-filled buffers. Exploitation requires Task Runners enabled, the Code Node available, and permission to execute task code; disclosure is limited to residual data in the same Node.js process.
The record
- CVE
- CVE-2025-61917
- Published
- Feb 4, 2026
- Updated
- Feb 4, 2026
- Vendor
- n8n
- Product
- n8n
- Classifications
- CWE-668, CWE-200, T1005
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 4, 2026CVE publishedPublication date reported by the CVE source.
- Feb 4, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 1.65.0, < 1.114.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo