n8n 1.123.56 - Security Patch: Five Vulnerabilities in Dependencies Fixed

What changed

The 1.123.56 release remediates five security issues discovered in dependencies such as hono and vue-i18n. Those fixes are dependency upgrades and security patches bundled into the n8n 1.x maintenance stream. The maintainers have linked the pull request and commits addressing the vulnerable components.

Why it matters for businesses

Even when a platform's core code is secure, vulnerabilities in transitive dependencies can introduce risk - from client-side XSS in internationalization libraries to routing or header issues in lightweight HTTP frameworks. Organizations using older release branches (1.x) are particularly exposed if they haven't migrated to newer major releases. Unpatched dependency vulnerabilities can be weaponized to exfiltrate credentials, execute malicious scripts for users, or degrade service integrity.

Recommended actions for leaders

Treat this as a high-priority security update: schedule an immediate upgrade for any instances running n8n 1.x, validate the fixes in staging, and deploy with monitoring for any regression. Maintain a software bill of materials (SBOM) and use SCA tools to track transitive dependencies continuously. For longer-term risk reduction, plan migration to the actively maintained major version (2.x) and embed dependency scanning and automated patching into your release pipelines to reduce future exposure.