N8N · GHSA-pwj5-wwm6-g83j · AI agents & MCP
FIX → >= 1.123.89 +3
In n8n's Chat Trigger node, the setup GET webhook route skips the n8n User Auth check when the chat is embedded. An unauthenticated request can read the conversation history of a named session or run the workflow with attacker-supplied input.
first public Oct 28, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Only published Chat Trigger workflows in embedded chat mode that use n8n User Auth are exposed; hosted chat and basic auth setups are not described as affected. Teams running self-hosted n8n with embedded chat widgets on their websites should check those workflows first. Teams that do not use the Chat Trigger node in embedded mode can skip it.
Not affected if basic-auth, hosted-chat-only, no-chat-trigger
Who cares chat-trigger, embedded-chat, n8n, self-hosted
n8n --version or the package in npm ls n8n; versions below the fixed releases are exposed.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.
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.
If upgrading is not immediately possible, administrators should consider the following temporary mitigations:
These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
Upgrade to >= 1.123.89 +3
1.123.892.45.52.46.13.0.1