Chat Trigger Embedded Chat Does Not Enforce n8n User Auth on All Requests

Impact

The Chat Trigger exempted its setup GET webhook route from the n8n User Auth check in all chat modes. The exemption was intended only for hosted chat, where the route serves the chat page, but it also applied to embedded chat. On a published Chat Trigger configured with embedded chat mode and n8n User Auth, an unauthenticated GET request to the chat webhook URL bypassed authentication and could read the conversation history of a named session, or trigger the workflow with attacker-supplied input.

Patches

The issue has been fixed in n8n versions 1.123.89, 2.45.5, 2.46.1 and 3.0.1. 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:

• Restrict n8n instance access to fully trusted users only.
• Deactivate Chat Trigger workflows configured in embedded chat mode with n8n User Auth until the instance is patched.
• Apply network-level controls to restrict access to webhook endpoints.
• Switch affected Chat Trigger workflows to basic auth if embedded chat mode must remain active.

These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.