CVE-2026-56353 n8n vulnerability
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.
Quick answer
n8n should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- 2.10.0
Fixed versions
- Apply the latest vendor-supported patched version.
How to fix it
CVE-2026-56353 affects n8n and is rated medium. n8n contains an authentication bypass in the Chat Trigger node when configured with n8n User Auth (a non-default configuration). Fix this first on internet-facing or admin systems. The practical fix is to upgrade n8n to 1.123.22, 2.9.3, 2.10.1, or a later patched release, then verify the system is no longer exposed.
- Inventory every server, container, appliance, cluster, plugin, or device that uses n8n.
- Check the installed version and configuration against CVE-2026-56353 and the linked advisory.
- Apply the vendor fix: upgrade n8n to 1.123.22, 2.9.3, 2.10.1, or a later patched release.
- Limit workflow, credential, webhook, and external secret access to trusted users only.
- Disable or isolate the affected feature if you cannot update right away.
- Review workflow runs, credential changes, webhook hits, and external secret use for suspicious activity.
- Rotate secrets, rebuild affected systems, or reset sessions if you suspect compromise.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm n8n is running the patched version or the approved mitigation is active.
- Confirm affected public, admin, API, tunnel, or cluster access is limited to trusted users.
- Repeat the risky workflow or a safe test case and confirm the issue no longer appears.
- Review logs again after the fix for crashes, bypass attempts, file access, or suspicious changes.
- Save version, config, log, and scan evidence for your remediation record.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-56353?
n8n versions listed as affected should be reviewed: 2.10.0.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.