n8n has a Guardrail Node Bypass
Medium3.7CVE-2026-56349 · Published Feb 26, 2026 · updated Jul 16, 2026
## Impact An end user interacting with a workflow that uses the Guardrail node could craft an input that bypasses the default guardrail instructions. ## Patches The issue has been fixed in n8n version 2.10.0. Users should upgrade to this version or later to remediate the vulnerability. ## Workarounds If upgrading is not immediately possible, administrators should consider the following temporary mitigations: - Limit access to trusted users. - Review asses the practical impact of guardrail bypasses in your usecase and adjust your workflow accordingly. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
Affected versions
| Package | Affected | Fixed in |
|---|---|---|
| n8n npm | < 2.10.0 | 2.10.0 |
Details and references
More n8n advisories
All n8n| Date | Advisory | Severity | Fixed in |
|---|---|---|---|
| Feb 26 | n8n has Webhook Forgery on Zendesk Trigger Node | Medium4.0 | 1.123.18+1 more |
| Feb 26 | n8n has an Authentication Bypass in its Chat Trigger Node | Medium4.8 | 1.123.22+2 more |
| Feb 26 | n8n has an SSO Enforcement Bypass in its Self-Service Settings API | Medium6.3 | 2.8.0 |
| Feb 26 | n8n: Webhook Forgery on Github Webhook Trigger | Medium4.0 | 1.123.15+1 more |
| Feb 26 | n8n: SQL Injection in MySQL, PostgreSQL, and Microsoft SQL nodes | Medium8.2 | 2.4.0 |
| Feb 25 | n8n Vulnerable to Stored XSS via Various Nodes | High5.4 | 1.123.22+2 more |