UTC
Medium

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

GHSA-pwj5-wwm6-g83j · published 2026-10-28

Severity
Medium
CVSS score
6.3
Chance of exploitation (EPSS)
No CVE
Fixed in
3.0.1
What it is

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.

What to do

Upgrade n8n to 3.0.1 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.

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 you cannot upgrade yet

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.

Affected
PackageRegistryAffectedFixed in
n8nnpm< 1.123.891.123.89
n8nnpm< 2.45.52.45.5
n8nnpm< 2.46.12.46.1
n8nnpm< 3.0.13.0.1

The impact, patch and workaround text comes from the advisory, shortened (published by n8n). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].