CVE-2026-33660: n8n Workflow Merge Node Bug - What It Means for Your Business and How to Respond

CVE-2026-33660 represents a critical vulnerability in n8n, a widely used open-source workflow automation platform that connects apps, APIs, and services to streamline your operations. If you rely on n8n to automate tasks like data transfers or process triggers, this flaw could allow attackers to run unauthorized code on your servers, disrupting services and exposing sensitive information. This post explains the business implications in plain terms, helps you assess your exposure, and provides clear steps to protect your organization, with technical details reserved for your IT team in the appendix.

S1 — Background & History

n8n publicly disclosed CVE-2026-33660 on March 24, 2026, through the National Vulnerability Database (NVD). The vulnerability affects n8n, an open-source tool for automating workflows across business applications. Security researchers identified the issue, with Qualys ThreatPROTECT reporting it on March 30, 2026.

The flaw carries a CVSS v4.0 base score of 9.4, classifying it as critical severity. In simple terms, it stems from inadequate restrictions in a database sandbox, enabling improper data handling that leads to remote code execution. Key timeline events include the initial report in late March 2026, patches released in versions 2.14.1, 2.13.3, and 1.123.26, and immediate vendor advisories urging upgrades. No widespread exploits appeared in the first week post-disclosure, but the high score underscores the urgency for n8n users.

S2 — What This Means for Your Business

You face direct operational risks if attackers exploit CVE-2026-33660, as it allows authenticated users with workflow edit access to execute code on your n8n servers. This could halt automated processes critical to your daily operations, such as syncing customer data between CRM and ERP systems, leading to delays in order fulfillment or reporting. Your business data becomes vulnerable too; attackers might steal customer records, financial details, or proprietary workflows, resulting in costly breaches under laws like the California Consumer Privacy Act or Canada's Personal Information Protection and Electronic Documents Act.

Reputationally, a compromise signals weak security controls to clients and partners, eroding trust in your brand, especially if downtime affects service delivery. Compliance obligations amplify the stakes: failure to secure automation tools could trigger audits, fines from the Federal Trade Commission, or requirements under frameworks like SOC 2 or ISO 27001. Ultimately, you risk not just immediate losses from disruption but long-term revenue hits from lost business and remediation expenses, making swift action essential to safeguard your continuity.

S3 — Real-World Examples

Regional Bank's Data Pipeline Halt: A mid-sized U.S. bank uses n8n to automate transaction reconciliations between core banking software and accounting systems. An insider with workflow access exploits the flaw, executing code that corrupts daily reports and exposes customer account details. Operations freeze for hours, delaying wire transfers and incurring regulatory reporting penalties.

Canadian Retailer's Supply Chain Breach: A Toronto-based retailer automates inventory updates across e-commerce platforms and warehouses via n8n. Attackers compromise a vendor-shared workflow, reading server files to steal supplier contracts and pricing data. The breach leaks to media, prompting customer refunds and a 15% sales dip amid trust erosion.

Healthcare Provider's Patient Workflow Disruption: A U.S. clinic chain relies on n8n for scheduling integrations with electronic health records. The vulnerability lets a malicious employee run code, disrupting appointment syncs and exposing protected health information. HIPAA investigations follow, with fines exceeding $500,000 and temporary service outages.

Manufacturing Firm's Production Downtime: An Ontario manufacturer automates order processing from sales tools to factory systems using n8n. Exploitation halts production lines by injecting faulty commands, causing a full shift loss and supply delays to key clients.

S4 — Am I Affected?

• You use n8n for workflow automation in versions prior to 2.14.1, 2.13.3, or 1.123.26.

• Your team grants workflow creation or modification permissions to users beyond fully trusted administrators.

• n8n instances handle sensitive business data, customer information, or operational processes exposed to internal networks.

• You lack segmentation isolating n8n servers from core business systems like databases or financial apps.

• Automated workflows involve merging data via SQL modes in the Merge node, increasing exploit potential.

• Your organization operates in regulated sectors like finance, healthcare, or manufacturing without recent vulnerability scans.

OUTRO

Key Takeaways

• CVE-2026-33660 enables remote code execution in n8n via flawed Merge node SQL handling, risking your operational continuity.

• You must verify n8n versions and user permissions immediately to gauge exposure and prevent data theft or downtime.

• Business impacts include compliance fines, reputational damage, and revenue loss from disrupted automations.

• Upgrade to patched versions or apply interim controls like restricting workflow edits to trusted users.

• Engage experts for penetration testing to uncover hidden risks in your automation stack.

Call to Action

Secure your n8n deployments today by scheduling a penetration test with IntegSec. Our specialists deliver precise vulnerability triage and customized risk reduction, ensuring your USA or Canada operations stay resilient against threats like CVE-2026-33660. Visit https://integsec.com to book your assessment and fortify your defenses confidently.

TECHNICAL APPENDIX (security engineers, pentesters, IT professionals only)

A — Technical Analysis

The root cause lies in the AlaSQL JavaScript SQL engine's inadequate sandboxing within n8n's Merge node's "Combine by SQL" mode. Attackers with authenticated access to create or modify workflows craft malicious SQL statements that bypass restrictions, reading arbitrary local files or executing system commands for full remote code execution (RCE). The attack vector is network-based over HTTP/HTTPS, with low complexity, no user interaction required beyond initial authentication, and low privileges (workflow edit rights).

CVSS v4.0 vector is CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H, yielding the 9.4 score. NVD reference: https://nvd.nist.gov/vuln/detail/CVE-2026-33660. CWE-159: Insufficient Sandboxing of Helper Mechanism.

B — Detection & Verification

Version Enumeration:

• Query n8n API endpoint /api/v1/workflows or check docker image inspect for tags <2.14.1/2.13.3/1.123.26.

• Run curl -u <user>:<pass> http://<n8n-host>/rest/workflows and inspect response headers or body for version metadata.

Scanner Signatures:

• Nessus/Tenable plugins for CVE-2026-33660; Qualys QID matching AlaSQL bypass patterns.

• Nuclei template: YAML detecting Merge node SQL injection via AlaSQL payloads.

Log Indicators:

• n8n logs show AlaSQL errors or unexpected file reads (e.g., /etc/passwd attempts in merge-node.log).

• Audit logs record workflow creations with SQL "Combine" mode using non-standard queries.

Behavioral Anomalies:

• Sudden CPU spikes or file I/O on n8n host during workflow execution; anomalous outbound connections from automation server.

Network Exploitation Indicators:

• HTTP POST to /webhook/* or /api/v1/workflows with AlaSQL payloads like LOAD DATA LOCAL INFILE.

C — Mitigation & Remediation

• Immediate (0–24h): Revoke workflow create/edit permissions from non-trusted users; set NODES_EXCLUDE=n8n-nodes-base.merge environment variable and restart n8n.

• Short-term (1–7d): Upgrade to n8n 2.14.1, 2.13.3, or 1.123.26+ via Docker/pip; verify with n8n --version; enable workflow approval gates.

• Long-term (ongoing): Implement role-based access with least privilege; segment n8n in isolated VLAN; deploy WAF rules blocking SQL injection in Merge payloads; schedule regular pentests.

D — Best Practices

• Enforce principle of least privilege for workflow permissions, auditing access quarterly.

• Disable unused nodes via NODES_EXCLUDE and validate all SQL inputs in custom workflows.

• Containerize n8n with read-only filesystems and non-root users to limit RCE impact.

• Integrate vulnerability scanners like Trivy into CI/CD for image checks pre-deployment.

• Monitor AlaSQL execution via extended logging and SIEM rules for sandbox escapes.