INCIDENT MAP

Browse / AI Framework and Platform Flaws / CVE-2026-59209

n8n: Shared Credential Header Leak via HTTP Request Pagination Expression

CVE-2026-59209 ยท 2026-07-22 high

Class
AI Framework and Platform Flaws (filed by a model that read the advisory)
Technique
Data exfiltration
Affected
n8n (npm)
Gets past
Authorisation check
CVSS
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
EPSS
0.4% chance of exploitation in 30 days

How it works, in short

A user with use-only workflow access reads a shared HTTP Header Auth secret from pagination request state, then copies it into item data and sends it onward. (Our summary, written by a model. The source text is below.)

Details

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.

References

Source: GitHub Advisory Database, used under CC BY 4.0.