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.
Affected versions
| Package | Affected | Fixed in |
|---|---|---|
| n8n npm | < 1.123.22 | 1.123.22 |
| >= 2.0.0, < 2.9.3 | 2.9.3 | |
| >= 2.10.0, < 2.10.1 | 2.10.1 |
Details and references
- CVSS 3.1
- CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
- Severity from
- GitHub (reviewed advisory)
- Weakness
- CWE-287
- Also known as
- CVE-2026-56353
More n8n advisories
All n8n| Date | Advisory | Severity | Fixed in |
|---|---|---|---|
| Feb 26 | n8n has Webhook Forgery on Zendesk Trigger Node | Medium4.0 | 1.123.18+1 more |
| Feb 26 | n8n has a Guardrail Node Bypass | Medium3.7 | 2.10.0 |
| Feb 26 | n8n has an SSO Enforcement Bypass in its Self-Service Settings API | Medium6.3 | 2.8.0 |
| Feb 26 | n8n: Webhook Forgery on Github Webhook Trigger | Medium4.0 | 1.123.15+1 more |
| Feb 26 | n8n: SQL Injection in MySQL, PostgreSQL, and Microsoft SQL nodes | Medium8.2 | 2.4.0 |
| Feb 25 | n8n Vulnerable to Stored XSS via Various Nodes | High5.4 | 1.123.22+2 more |