Monitor vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
6.3
n8n's Chat Trigger Node Fails to Verify User Authentication
GHSA-jh8h-6c9q-7gmw
Summary
If you're using n8n's Chat Trigger node with user authentication, an attacker could potentially bypass security checks. This is a concern if you're allowing users to create or edit workflows. To fix this, update to n8n version 2.10.1 or later. If an update isn't possible, limit user permissions or use a different authentication method for the node.
What to do
- Update GitHub Actions n8n to version 1.123.22.
- Update GitHub Actions n8n to version 2.9.3.
- Update GitHub Actions n8n to version 2.10.1.
Affected software
| Vendor | Product | Affected versions | Fix available |
|---|---|---|---|
| GitHub Actions | n8n | <= 1.123.22 | 1.123.22 |
| GitHub Actions | n8n | > 2.0.0 , <= 2.9.3 | 2.9.3 |
| GitHub Actions | n8n | > 2.10.0 , <= 2.10.1 | 2.10.1 |
Original title
n8n has an Authentication Bypass in its Chat Trigger Node
Original description
## 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.
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.
ghsa CVSS3.1
4.8
ghsa CVSS4.0
6.3
Vulnerability type
CWE-287
Improper Authentication
- https://github.com/n8n-io/n8n/security/advisories/GHSA-jh8h-6c9q-7gmw
- https://github.com/n8n-io/n8n/commit/062644ef786b6af480afe4a0f12bc6d70040534a
- https://github.com/n8n-io/n8n/commit/1479aab2d32fe0ee087f82b9038b1035c98be2f6
- https://github.com/n8n-io/n8n/commit/9e5212ecbc5d2d4e6f340b636a5e84be6369882e
- https://github.com/advisories/GHSA-jh8h-6c9q-7gmw
Published: 26 Feb 2026 · Updated: 7 Mar 2026 · First seen: 6 Mar 2026