UTC
Medium

Credential-Using Nodes Forward Authentication Headers on Cross-Origin Redirects

GHSA-prmc-fg87-r4gh · published 2026-10-28

Severity
Medium
CVSS score
6.3
Chance of exploitation (EPSS)
No CVE
Fixed in
3.0.1
What it is

When an HTTP request made by a credential-authenticated node followed a redirect to a different origin, n8n re-attached the Authorization header and basic auth credentials to the redirected request. The internal helper that builds the redirect configuration defaulted sendCredentialsOnCrossOriginRedirect to true. The HTTP Request node v4.4 opted out of this default, but other credential-using nodes did not. Where a workflow makes authenticated HTTP requests and the redirect target can be influenced by untrusted data, such as an expression-fed URL or a redirect issued by an attacker-controlled endpoint, the stored credential could be forwarded to an unintended destination.

What to do

Upgrade n8n to 3.0.1 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.

The issue has been fixed in n8n versions 2.46.1, 2.45.5 and v3.0.1. Users should upgrade to one of these versions or later to remediate the vulnerability.

If you cannot upgrade yet

If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Restrict n8n instance access to fully trusted users only. Audit active workflows that use credential-authenticated HTTP requests and ensure that request URLs and any data that could influence redirect targets do not incorporate untrusted external input. Apply network-level controls to restrict outbound HTTP requests from the n8n process to known, trusted destinations. Enable SSRF protection by setting N8N_SSRF_PROTECTION_ENABLED=true to reduce the risk of attacker-influenced outbound requests. …

Affected
PackageRegistryAffectedFixed in
n8nnpm< 2.45.52.45.5
n8nnpm< 2.46.12.46.1
n8nnpm< 3.0.13.0.1

The impact, patch and workaround text comes from the advisory, shortened (published by n8n). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].