n8n fixes a batch of high-severity flaws, including SQL injection, code execution and an approval bypass: update to 2.42.1 or 2.41.4

n8n fixes a batch of high-severity flaws, including SQL injection, code execution and an approval bypass: update to 2.42.1 or 2.41.4

2 October 2026: n8n, the workflow-automation platform that many companies run on their own servers to connect business systems and AI agents, published ten security advisories on its code repository on 30 September 2026. Eight are rated high and two moderate. Italy's national CSIRT issued an alert on 1 October listing eleven high-severity CVEs in n8n, and the Canadian Centre for Cyber Security published an advisory the same day.

Update, 26 October 2026: n8n's advisory list now gives patched versions for every advisory in this batch: 2.42.1 and 2.41.4 for most, 1.123.83 for those that also affect the 1.x line, and 2.42.0 or 2.41.4 for the chat-resume flaw; none carries a CVE number yet. A second batch of advisories published on 14 October needs 2.44.1, 2.43.5 or 1.123.85 (one of them is fixed from 2.42.2 or 2.41.5), so the versions in the title are no longer the newest safe floor.

The flaws

Among the advisories of 30 September:

• SQL injection in the Microsoft SQL node through expression interpolation into the query field.
• Code execution in the Git node's log operation through repository configuration that is not neutralised.
• Send-and-wait HMAC bypass: someone holding an execution's resume token can approve a waiting step without proper authorisation, so a workflow can run on under its owner's credentials. n8n rates it 7.0 and fixes it in 2.42.1 and 2.41.4.
• Owner account takeover through shared-prototype mutation in the MCP workflow-validation interpreter.
• Unauthenticated, unbounded OAuth client persistence through the authorize endpoint.
• A shared-workflow credential check that misses nested and inline sub-workflows, so credentials can be reached in ways the sharing model did not intend.
• Stored cross-site scripting in the Chat Trigger's hosted chat page and in the binary-data file preview.

The Italian alert gives the affected ranges for the CVEs it lists as versions before 1.123.80, 2.0.0 to 2.39.5, and 2.40.0. Each GitHub advisory names its own patched versions.

Not yet independently verified. The patched versions are confirmed for two advisories: the HMAC bypass, and the Microsoft SQL node injection, catalogued on 14 October as CVE-2026-110840, both fixed in 2.42.1 and 2.41.4. The remaining advisories were read from n8n's list, which does not show versions.

What to do

• Update self-hosted n8n to 2.42.1 or 2.41.4 (or later) on the 2.x line. If you are still on 1.x, take the newest 1.123 release and plan the move to 2.x.
• Open each advisory that matches a node you use (Microsoft SQL, Git, Chat Trigger, send-and-wait, MCP tools) and check its fixed version against yours.
• Review who can create, edit and share workflows: several flaws need an authenticated user, so a large editor group widens the risk.
• Rotate credentials stored in n8n if your instance is exposed to the internet and was unpatched, and review recent executions for approvals nobody made.
• On n8n Cloud, ask whether your instance has been updated.

Why it matters

Workflow-automation servers hold credentials for the systems they connect: CRM, finance, email, databases and now AI agents. A flaw that lets one user reach another's credentials, or run code on the server, exposes all of them at once.

Related on TrustList:

• Digiwin EasyFlow .NET has critical flaws allowing unauthenticated code execution and password theft, Taiwan’s CERT warns

Sources

• n8n security advisories (GitHub), including GHSA-728h-pmr2-7cgh - 30 September 2026
• CSIRT Italia (ACN): Rilevate vulnerabilità in n8n (AL07/261001/CSIRT-ITA) - 1 October 2026
• Canadian Centre for Cyber Security: n8n security advisory (AV26-985) - 1 October 2026
• n8n security advisories (GitHub), including the 14 October 2026 batch (read 26 October 2026) - 26 October 2026
• VulnCheck: n8n before 2.41.4 and 2.42.1 SQL injection via Microsoft SQL node query field (CVE-2026-110840) - 14 October 2026