CVE-2026-56353
mediumpriority · track · 0EPSS 0.003 · 26 %ileDEEUNLUSEPSS · scored 2026-10-27
n8n contains an authentication bypass in the Chat Trigger node when configured with n8n User Auth (a non-default configuration). In affected releases — before 1.123.22, the 2.0.0 through 2.9.2 line, and 2.10.0 — the authentication check on the Chat Trigger webhook endpoint can be circumvented, allowing access without valid credentials. Fixed in 1.123.22, 2.9.3, and 2.10.1.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · low–medium · 1.7–6.3
ssvc
A stakeholder decision — act, attend, or track — from exploitation and impact.
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (11)
Products and version ranges known to be affected.
advisories (3)
Vendor and ecosystem advisories describing this.
- NCSC-2026-0248Kwetsbaarheden verholpen in n8n workflow automation platformNL2026-07-17csaf · ncsc_nlNL
n8n heeft meerdere kwetsbaarheden verholpen in het n8n workflow automation platform, specifiek in versies voor 2.10.1, 2.9.3, 1.123.22 en andere gerelateerde releases.
- WID-SEC-W-2026-0532n8n: Mehrere SchwachstellenDeutsch2026-02-25csaf · cert_bundDE
Ein Angreifer kann mehrere Schwachstellen in n8n ausnutzen, um beliebigen Programmcode auszuführen, um Sicherheitsvorkehrungen zu umgehen, um Daten zu manipulieren, um einen SQL-Injection Angriff durchzuführen, und um einen Cross-Site Scripting Angriff durchzuführen.
- GHSA-jh8h-6c9q-7gmwn8n has an Authentication Bypass in its Chat Trigger Node2026-02-26ghsa · osvUS
## 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.
also known as (3)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (6)
External citations — patches, advisories, analysis.
- https://github.com/n8n-io/n8n/security/advisories/GHSA-jh8h-6c9q-7gmwcnnvd
- https://www.vulncheck.com/advisories/n8n-authentication-bypass-in-chat-trigger-nodecnnvd
- https://github.com/n8n-io/n8n/security/advisories/GHSA-jh8h-6c9q-7gmwenisa_euvd
- https://www.vulncheck.com/advisories/n8n-authentication-bypass-in-chat-trigger-nodeenisa_euvd
- https://github.com/n8n-io/n8n/security/advisories/GHSA-jh8h-6c9q-7gmwVendor Advisorynvd
- https://www.vulncheck.com/advisories/n8n-authentication-bypass-in-chat-trigger-nodeThird Party Advisorynvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan