Cpe:2.3:a:n8n:n8n:*:*:*:*:community:node.js:*:* - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/cpes/cpe2.3an8nn8ncommunitynode.js/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioWed, 22 Jul 2026 21:56:24 +0000n8n Shared Credential Leakage via HTTP Request Pagination Vulnerabilityhttps://feed.craftedsignal.io/briefs/2026-07-n8n-credential-leak/Wed, 22 Jul 2026 21:56:24 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-07-n8n-credential-leak/An authenticated n8n user with 'use-only editor access' can exploit CVE-2026-59209 in shared workflows when `N8N_EXPRESSION_ENGINE=vm` is enabled, allowing them to read sensitive HTTP Header Auth credentials from the `$request.headers` object within a paginated HTTP Request node's expression and exfiltrate them, bypassing credential domain restrictions.A high-severity vulnerability, CVE-2026-59209, exists in the n8n workflow automation platform, allowing authenticated users with "use-only editor access" to leak sensitive credentials. This flaw occurs in instances where the N8N_EXPRESSION_ENGINE environment variable is set to vm and shared workflows utilize HTTP Request nodes with HTTP Header Auth credentials and pagination enabled. Attackers can craft malicious expressions within the pagination settings of such nodes to access and extract the HTTP Header Auth secret from the $request.headers object. The extracted secret can then be embedded into item data and subsequently exfiltrated via another HTTP Request node, effectively bypassing credential domain restrictions. This vulnerability impacts n8n versions prior to 1.123.61, versions 2.28.0 through 2.28.1, and versions 2.0.0-rc.0 through 2.27.4.

Attack Chain

  1. An authenticated n8n user with "use-only editor access" gains access to a shared workflow.
  2. The n8n instance is configured with N8N_EXPRESSION_ENGINE=vm.
  3. The shared workflow contains an HTTP Request node that uses HTTP Header Auth credentials and has pagination enabled.
  4. The malicious user identifies this configuration and crafts an arbitrary expression within the pagination settings.
  5. This crafted expression is evaluated and accesses the $request.headers object, which contains the sensitive HTTP Header Auth secret.
  6. The expression extracts the secret and copies it into the workflow's item data.
  7. The item data, now containing the credential secret, is sent to a subsequent HTTP Request node configured to exfiltrate data to an attacker-controlled external endpoint.
  8. The sensitive HTTP Header Auth credential is exfiltrated, bypassing n8n's credential domain restrictions.

Impact

The successful exploitation of CVE-2026-59209 allows lower-privileged, authenticated users to gain unauthorized access to sensitive HTTP Header Auth credentials. This enables them to bypass intended credential domain restrictions, potentially leading to unauthorized access to external services or systems integrated with n8n. The vulnerability can facilitate data exfiltration if the compromised credentials provide access to sensitive data sources. This issue affects specific configurations of n8n and poses a significant risk to organizations using shared workflows with credential-populated headers.

Recommendation

  • Upgrade n8n instances immediately to remediate CVE-2026-59209. Affected versions are < 1.123.61, >= 2.28.0, < 2.28.1, and >= 2.0.0-rc.0, < 2.27.4.
  • Restrict workflow sharing to fully trusted users only to mitigate the risk of CVE-2026-59209.
  • Avoid sharing credentials with use-only access to untrusted users, especially on workflows that employ HTTP Request nodes with pagination enabled.
]]>highadvisoryn8nvulnerabilitycredential-accessdata-exfiltrationapplication-securityprototype-pollutionauthentication-bypassdata-enumeration