GHSA-q3j5-8vrg-4p9q n8n: Shared Credential Header Leak via HTTP Request Pagination Expression

• 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 member with use-only editor access to a shared workflow could read credential-populated headers exposed via the `$request` object inside an HTTP Request node's pagination expression. When an HTTP Header Auth credential is applied to a paginated request, the secret is present in `$request.headers` when pagination expressions are evaluated. A user-controlled expression could read that secret, copy it into item data, and exfiltrate it through a later HTTP Request node, bypassing credential domain restrictions, since the secret leaves via item data rather than the credential's own request mechanism. This issue only affects instances with `N8N_EXPRESSION_ENGINE=vm` set, where paginated HTTP Request workflows using shared credentials are accessible to non-owner users. 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 sharing to fully trusted users only. • Avoid sharing credentials with use-only access to untrusted users on workflows that use HTTP Request nodes with pagination enabled. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.