CVE-2026-126389

n8n embedded chat could bypass user authentication

n8n-io · n8n Chat Trigger

First documented disclosure · Review checkpoint

Summary

Unauthenticated requests could read a named chat session or start its workflow.

Severity and exploitation evidence

Medium · 6.3/10 · CVSS 4.0. Severity source.

Exploitation not established: Malicious exploitation remains unverified in the reviewed sources.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

An authentication exemption intended for hosted chat also covered the embedded-chat setup route.

Conditions required

A published Chat Trigger uses embedded chat mode and n8n User Auth; the attacker knows the webhook URL and, for history access, a session identifier.

Potential impact

Conversation history can be disclosed and workflows can receive attacker-supplied input.

Affected versions and configurations

Before 1.123.89; 2.x before 2.45.5; 2.46.0 before 2.46.1; and 3.0.0 before 3.0.1.

Fix and mitigation status

1.123.89, 2.45.5, 2.46.1 and 3.0.1.

Practical next steps

Upgrade the applicable branch. Until patched, deactivate affected embedded Chat Triggers or restrict webhook access; the maintainer also identifies basic authentication as a temporary option.

Operating lesson

Apply authentication consistently across all chat transport routes.

Evidence and limits

Original public disclosure 2026-10-28; CVE publication 2026-11-13. This historical disclosure was absent from the register. The CNA explicitly links the otherwise unnumbered GitHub advisory.

Sources