n8n's free self-hosted edition is a popular alternative to Zapier and Make. Its October 14 security update is a useful reminder of what "free" can cost in maintenance.
According to n8n's community security bulletin dated October 14, 2026, the company disclosed 15 security advisories: five rated High and ten rated Medium. The High items include stored cross-site scripting through webhook responses, a crafted workflow ID that could expose data tables in other projects, a prototype pollution issue that can cause denial of service, a glob pattern in the Read/Write Files node that can block the event loop, and credential secrets appearing in the execution error data of several nodes.
The Medium items cover a range of nodes and features, including the Slack Trigger webhook, the Quick Base and Microsoft Outlook/SharePoint nodes, Chat Hub, and several credential-permission checks. Full details are in the advisories on n8n's GitHub repository. Third-party coverage notes the advisories had no CVE IDs at the time, so they are tracked by GitHub advisory (GHSA) identifiers.
The bulletin says affected n8n Cloud instances are patched automatically and need no action. Self-hosted users below the fixed versions should upgrade: 1.123.85 on the v1 line, 2.43.5 or later on stable, or 2.44.1 or later on beta. If you are already on the latest patch for your branch, no action is needed. Stay on your own release branch rather than jumping between them.
One third-party write-up says the Slack Trigger issue can be exploited without logging in, which would make internet-reachable webhooks the most exposed setup. We have not independently verified that, so read the official advisory for your configuration.
A separate report, as summarized in a community post, says security firm Censys counted roughly 114,000 internet-exposed n8n hosts, and that most of those with a detectable version were running a version affected by at least one recent critical vulnerability. We have not reviewed the Censys report directly, so treat those figures as indicative rather than confirmed.
The official bulletin does not list workarounds for instances that cannot upgrade right away, so some third-party mitigation suggestions are unofficial and worth treating with caution.
| Option | Who handles patching | Best fit |
|---|---|---|
| n8n self-hosted | You | Technical teams with someone responsible for hosting, updates and security |
| n8n Cloud | n8n (per the bulletin) | Teams that like n8n's approach but do not want to run servers |
| Zapier / Make | The vendor | Non-technical teams who want hosted tools with less operational work |
This is not a claim that managed tools are risk-free. Any platform that stores your credentials is a security decision, and Zapier and Make have their own security pages worth reading. The difference is who is responsible for applying fixes on a given day. With self-hosting, that is you.
For pricing and feature differences between the managed tools, see our Make vs Zapier breakdown. For what else n8n shipped recently, see our n8n Browser Use and cost tracking explainer.
Self-hosted n8n saves on license fees, but a batch of 15 advisories is a fair test of whether your team can keep it patched. If you have the skills and the time, update now and set a recurring check. If you do not, n8n Cloud or a managed platform likely costs less than an incident.
Note that StackPilot's comparisons are based on research of public information and vendor documentation, not hands-on testing. This is not security advice; confirm details in n8n's official advisories.