cve.bz

CVE-2026-126388 n8n before 2.46.1 Credential Leak via Cross-Origin Redirects in Nodes

6.3 mediumEPSS 0.3%

Medium (6.3) in n8n-io n8n. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
n8n before 2.46.1 contains a credential exposure vulnerability that forwards Authorization headers and basic auth credentials on cross-origin redirects because sendCredentialsOnCrossOriginRedirect defaults to true. Attackers controlling a redirect target or an expression-fed URL in credential-using nodes can capture stored workflow credentials sent to their endpoint.

Severity

CVSS 4.0

6.3 medium
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

CVSS 3.1

3.7 low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS
0.3% estimated probability of exploitation activity in the next 30 days; 23rd percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-522 Insufficiently Protected Credentials
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
Assigned by
VulnCheck (CNA)
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-126388 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-126388?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-126388?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-126388 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-126388

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-126388](https://cve.bz/cve/badge/CVE-2026-126388.svg)](https://cve.bz/cve/CVE-2026-126388)

HTML:

<a href="https://cve.bz/cve/CVE-2026-126388"><img src="https://cve.bz/cve/badge/CVE-2026-126388.svg" alt="CVE-2026-126388"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
n8n-io n8nfrom 2.46.0 before 2.46.1
n8n-io n8nbefore 2.45.5
n8n-io n8nfrom 3.0.0 before 3.0.1

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-522 (13).

History

  1. The NVD deferred its analysis

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON