Skip to content
n8nGHSA-jh8h-6c9q-7gmw

n8n has an Authentication Bypass in its Chat Trigger Node

Medium4.8CVE-2026-56353 · Published Feb 26, 2026 · updated Jul 16, 2026

## Impact When the Chat Trigger node is configured with n8n User Auth authentication, the authentication check could be circumvented. - This issue requires the Chat Trigger node to be configured with n8n User Auth authentication (non-default). ## Patches The issue has been fixed in n8n versions 2.10.1, 2.9.3, and 1.123.22. Users should upgrade to one of these versions or later to remediate the vulnerability. ## Workarounds If upgrading is not immediately possible, administrators should consider the following temporary mitigations: - Limit workflow creation and editing permissions to fully trusted users only. - Use a different authentication method for the Chat Trigger node, or restrict network access to the webhook endpoint to trusted origins. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

GitHub advisory

Affected versions

PackageAffectedFixed in
n8n
npm
< 1.123.221.123.22
>= 2.0.0, < 2.9.32.9.3
>= 2.10.0, < 2.10.12.10.1
Details and references

More n8n advisories

All n8n
Advisory
n8n has Webhook Forgery on Zendesk Trigger Node
Medium4.0Feb 26
n8n has a Guardrail Node Bypass
Medium3.7Feb 26
n8n has an SSO Enforcement Bypass in its Self-Service Settings API
Medium6.3Feb 26
n8n: Webhook Forgery on Github Webhook Trigger
Medium4.0Feb 26
n8n: SQL Injection in MySQL, PostgreSQL, and Microsoft SQL nodes
Medium8.2Feb 26
n8n Vulnerable to Stored XSS via Various Nodes
High5.4Feb 25

Critical advisories by email

Wednesdays: the week’s critical and high advisories in the AI and data stack, with the fixed versions. Only in weeks that have some.

Double opt-in. Unsubscribe any time.