CVE-2026-42226

GHSA-r4v6-9fqc-w5jr HIGH
Published April 29, 2026

## Impact The `dynamic-node-parameters` endpoints did not verify whether the authenticated caller was authorized to use a supplied credential reference. An authenticated user with access to a shared workflow could supply a foreign credential ID in the request body, causing the backend to decrypt...

Full CISO analysis pending enrichment.

Affected Systems

Package Ecosystem Vulnerable Range Patched
n8n npm >= 2.17.0, < 2.17.5 2.17.5
185.6K OpenSSF 6.0 16 dependents Pushed 4d ago 38% patched ~1d to patch Full package profile →

Do you use n8n? You're affected.

Severity & Risk

CVSS 3.1
8.5 / 10
EPSS
N/A
Exploitation Status
No known exploitation
Sophistication
N/A

Attack Surface

AV AC PR UI S C I A
AV Network
AC Low
PR Low
UI None
S Changed
C High
I None
A Low

Recommended Action

Patch available

Update n8n to version 2.17.5

Compliance Impact

Compliance analysis pending. Sign in for full compliance mapping when available.

Frequently Asked Questions

What is CVE-2026-42226?

n8n's Credential Authorization Bypass in dynamic-node-parameters Allows Foreign API Key Replay

Is CVE-2026-42226 actively exploited?

No confirmed active exploitation of CVE-2026-42226 has been reported, but organizations should still patch proactively.

How to fix CVE-2026-42226?

Update to patched version: n8n 2.17.5.

What is the CVSS score for CVE-2026-42226?

CVE-2026-42226 has a CVSS v3.1 base score of 8.5 (HIGH).

Technical Details

NVD Description

## Impact The `dynamic-node-parameters` endpoints did not verify whether the authenticated caller was authorized to use a supplied credential reference. An authenticated user with access to a shared workflow could supply a foreign credential ID in the request body, causing the backend to decrypt and use that credential in a helper execution path where the caller also controls the destination URL. This allowed the caller to force the backend to authenticate against attacker-controlled infrastructure using a credential belonging to another user, effectively exfiltrating a reusable API key. The issue is not limited to any single node type; any node that resolves credentials dynamically through these endpoints may be affected. ## Patches The issue has been fixed in n8n version 2.18.0. Users should upgrade to this version or later to remediate the vulnerability. ## Workarounds If upgrading is not immediately possible, administrators should consider the following temporary mitigations: - Restrict n8n access to fully trusted users only. - Avoid sharing workflows with users who should not have access to the credentials those workflows reference. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

CVSS Vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L

Timeline

Published
April 29, 2026
Last Modified
April 29, 2026
First Seen
April 30, 2026

Related Vulnerabilities