Skip to content
MediumVulnerability

GHSA-jh8h-6c9q-7gmw: n8n has an Authentication Bypass in its Chat Trigger Node

Published
Record updated
View JSON
Affected
  • n8n >= 2.10.0, < 2.10.1, fixed in 2.10.1, released February 25, 2026, 1 day before disclosure
  • n8n >= 2.0.0, < 2.9.3, fixed in 2.9.3, released February 25, 2026, 1 day before disclosure
  • n8n < 1.123.22, fixed in 1.123.22, released February 25, 2026, 1 day before disclosure

Summary

The Chat Trigger node in n8n can be configured with n8n User Auth, a non-default authentication method. When that configuration is used, the authentication check can be circumvented. The issue requires this non-default configuration to be in place.

Mitigation

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. If upgrading is not immediately possible, 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 short-term measures.