CVE-2026-56354 n8n vulnerability
n8n before 1.123.24, 2.10.4, and 2.12.0 (across its 1.x and 2.x branches) contains cross-site scripting and open redirect vulnerabilities in the Form Node due to unsanitized HTML description fields and overly permissive iframe sandbox policies. Authenticated users with workflow creation permissions can inject malicious scripts or redirect parameters to perform stored XSS attacks or phishing redirects against end users.
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
- Review vendor advisory for affected versions.
Fixed versions
- Apply the latest vendor-supported patched version.
How to fix it
n8n is affected by CVE-2026-56354, a cross-site scripting exposure. n8n before 1.123.24, 2.10.4, and 2.12.0 (across its 1.x and 2.x branches) contains cross-site scripting and open redirect vulnerabilities in the Form Node due to unsanitized HTML description fields and overly permissive iframe sandbox policies. The recommended remediation is to update to n8n 1.123.24, 2.10.4, or 2.12.0 according to the deployed branch. Until the update is complete, restrict workflow creation permissions, Form Node usage, HTML descriptions, redirect parameters, and embedded form exposure, review logs, and reduce exposure of the affected service or workflow.
- Inventory every deployment, package, appliance, container, service, and managed environment that uses n8n.
- Confirm the installed version and compare it with versions before 1.123.24, 2.10.4, and 2.12.0 and the source advisory for CVE-2026-56354.
- Apply the vendor-supported fix: update to n8n 1.123.24, 2.10.4, or 2.12.0 according to the deployed branch.
- If the update cannot be applied immediately, restrict workflow creation permissions, Form Node usage, HTML descriptions, redirect parameters, and embedded form exposure; disable unnecessary public access, endpoints, plugins, integrations, or management interfaces until patched.
- Review application, device, reverse-proxy, WAF, package manager, container, authentication, and audit logs for activity related to CVE-2026-56354.
- Rotate sessions, API tokens, service credentials, integration keys, and administrator passwords if logs or affected data indicate compromise or unauthorized access.
- Clear caches, restart affected services, rebuild affected containers or appliances when appropriate, and remove temporary files or stored payloads created during exploitation attempts.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm n8n now reports n8n 1.123.24, 2.10.4, or 2.12.0 according to the deployed branch or a later vendor-supported fixed release for the deployed branch.
- Verify the affected workflow no longer allows the behavior described in CVE-2026-56354, using a safe regression test or vendor-provided validation method.
- Review logs after remediation for continued exploit attempts, denial-of-service symptoms, suspicious redirects, unauthorized requests, file access, or configuration changes.
- Rerun a Fixnx scan and any product-specific scanner, package audit, device health check, or manual regression test relevant to the affected service.
- Document affected assets, fixed versions, mitigation decisions, validation evidence, and any cleanup or credential rotation performed.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-56354?
n8n should be checked against the vendor advisory and trusted references linked on this page.
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.