---
id: CVE-2026-59209
aliases:
  - GHSA-q3j5-8vrg-4p9q
title: 'n8n: Shared Credential Header Leak via HTTP Request Pagination Expression'
summary: 'n8n: Shared Credential Header Leak via HTTP Request Pagination Expression'
severity: high
cwe:
  - CWE-200
vendor: n8n
product: n8n
ecosystem: npm
affected:
  - n8n < 1.123.61
  - 'n8n >= 2.28.0, < 2.28.1'
  - 'n8n >= 2.0.0-rc.0, < 2.27.4'
patched:
  - n8n 1.123.61
  - n8n 2.28.1
  - n8n 2.27.4
published: '2026-07-22'
updated: '2026-07-22'
source: GHSA
sourceUrl: 'https://github.com/advisories/GHSA-q3j5-8vrg-4p9q'
references:
  - url: 'https://github.com/n8n-io/n8n/security/advisories/GHSA-q3j5-8vrg-4p9q'
  - url: 'https://nvd.nist.gov/vuln/detail/CVE-2026-59209'
  - url: 'https://github.com/n8n-io/n8n/releases/tag/n8n%402.27.4'
  - url: 'https://github.com/n8n-io/n8n/releases/tag/n8n%402.28.1'
  - url: 'https://github.com/advisories/GHSA-q3j5-8vrg-4p9q'
tags:
  - ghsa
  - npm
epss: 0.00402
epssPercentile: 0.31677
ingestedAt: '2026-07-22T22:06:57.543Z'
---

## Overview

## 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.

## Affected packages

- `n8n < 1.123.61`
- `n8n >= 2.28.0, < 2.28.1`
- `n8n >= 2.0.0-rc.0, < 2.27.4`

## Remediation

Upgrade to a patched release:

- `n8n 1.123.61`
- `n8n 2.28.1`
- `n8n 2.27.4`