AI agent vulnerability · n8n

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

mediumCVSS 4.0 6.3 · 3.1 4.8

Impact When the Chat Trigger node is configured with n8n User Auth authentication, the authentication check could be circumvented. - This issue requires the Chat Trigger node to be configured with n8n User Auth authentication (non-default). Patches 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 to remediate the vulnerability.

Published Feb 26, 2026

Affected packages

n8n

Ecosystem: npm
Affected: < 1.123.22
Fixed in: 1.123.22
Check: npm ls n8n

n8n

Ecosystem: npm
Affected: >= 2.0.0, < 2.9.3
Fixed in: 2.9.3
Check: npm ls n8n

n8n

Ecosystem: npm
Affected: >= 2.10.0, < 2.10.1
Fixed in: 2.10.1
Check: npm ls n8n

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

Impact

When the Chat Trigger node is configured with n8n User Auth authentication, the authentication check could be circumvented.

This issue requires the Chat Trigger node to be configured with n8n User Auth authentication (non-default).

Patches

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 to remediate the vulnerability.

Workarounds

If upgrading is not immediately possible, administrators should consider the following temporary mitigations:

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 used as short-term mitigation measures.

Credited to sm1ee.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More n8n vulnerabilities

All n8n entries