Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
High

Information disclosure in n8n Task Runner via unsafe Buffer allocation

IdentifiersCVE-2025-61917CWE-244

CVE-2025-61917 is an information disclosure vulnerability in n8n affecting versions 1.65.0 through before 1.114.3. In the Task Runner context, untrusted code could access Node.js unsafe buffer allocation primitives, specifically Buffer.allocUnsafe() and Buffer.allocUnsafeSlow(). Because these APIs return uninitialized memory, an authenticated user able to execute code through n8n Task Runners could allocate buffers containing residual data from the same Node.js process. Exposed data could include contents left by prior requests or tasks, including secrets, tokens, and other sensitive runtime material. The issue was patched in 1.114.3, with content also indicating a fixed release in 1.115.0.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can disclose residual in-process memory from the n8n Node.js runtime. This may expose sensitive data handled earlier in the same process, such as secrets, tokens, credentials, or data from prior requests and workflow tasks. While the flaw does not itself provide code execution, the disclosed material could enable follow-on compromise, including credential theft, unauthorized API access, and broader compromise of workflows or connected services.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, disable the Code Node by adding n8n-nodes-base.code to the NODES_EXCLUDE environment variable. Also run Task Runners in external mode so untrusted task code executes in a separate sidecar container rather than in the main n8n process, reducing exposure to in-process memory disclosure. More generally, restrict which authenticated users are permitted to execute untrusted code in Task Runners.

Remediation

Patch, then assume compromise.

Upgrade n8n to a fixed version. The provided content states the issue is patched in 1.114.3 and also fixed in 1.115.0. The fix removes access to unsafe Buffer allocation functions from the Task Runner sandbox and uses zero-initialized allocation via Buffer.alloc(), with regression tests added.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
N8nN8napplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity3

Community discussion across Reddit, Mastodon, and other social sources.