GHSA-75qm-gp28-rcq9 n8n: Prototype Pollution via Workflow Credentials Leads to Unauthenticated User and Project Enumeration

• npm n8n: < 1.123.61 → fixed in 1.123.61 • npm n8n: >= 2.28.0, < 2.28.1 → fixed in 2.28.1 • npm n8n: >= 2.0.0-rc.0, < 2.27.4 → fixed in 2.27.4

Impact An authenticated user with the default `workflow:create` permission could pollute `Object.prototype` through a crafted workflow saved, updated, or imported via the workflow API. This can be leveraged to bypass authentication, allowing unauthenticated requests to be treated as a privileged user and exposing endpoints such as the user and project listings. As a result, every account's personal data (email, role, MFA status) and all projects on the instance may be disclosed to unauthenticated callers. The pollution can also corrupt global state, making parts of the instance unresponsive until restarted. Patches The issue has been fixed in n8n versions 1.123.61, 2.27.4, and 2.28.1. 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: • Restrict workflow creation and editing permissions to fully trusted users only. • Restrict network access to the n8n instance to trusted users only. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.