Understanding the n8n Credential Exfiltration Vulnerability
A significant security flaw, identified as CVE-2026-42226, has been discovered in n8n, the popular open-source workflow automation platform. This vulnerability could allow authenticated attackers to steal sensitive API keys and other credentials from other users within the system. This means that if an attacker has access to a shared workflow, they could potentially trick the system into revealing valuable secrets that belong to another user.
CVE Details
This vulnerability impacts n8n, an open-source workflow automation platform.
- Published Date: May 4, 2026
- Severity: High
- Status: Analyzed
Affected Products
The core issue lies in the dynamic-node-parameters endpoints within n8n. Specifically, versions of n8n prior to the following are affected:
- n8n versions before 1.123.33
- n8n versions before 2.17.5
Any n8n instance running these older versions is at risk if authenticated users can create or access shared workflows.
Current Status
The vulnerability has been officially “Analyzed,” meaning its details and impact are understood and confirmed by security researchers and the vendor.
Severity Level
CVE-2026-42226 is rated as High severity with a CVSS score of 7.5 (based on the original CVE data, and confirmed as High by GitHub Advisory with a CVSS v4 score of 7.1). This high rating reflects the serious risk associated with unauthorized access to sensitive credentials. An attacker with low privileges could exploit this flaw over the network without user interaction, leading to a high impact on the confidentiality of information. This essentially means that sensitive data, like API keys, could be easily stolen, potentially compromising other systems or services connected to n8n.
Possible Solutions
The good news is that n8n has already released patches to address this critical vulnerability. Users are strongly advised to upgrade their n8n installations to the following versions or newer:
- Version 1.123.33 or later
- Version 2.17.5 or later
- Version 2.18.0 or later
Upgrading is the most effective way to protect your n8n instance from this flaw. If immediate upgrading is not feasible, temporary mitigation steps include:
- Restrict User Access: Limit n8n access to only fully trusted users.
- Review Workflow Sharing: Avoid sharing workflows with users who do not require access to the specific credentials referenced within those workflows.
Please note that these workarounds are temporary and do not fully eliminate the risk. A full upgrade to the patched versions is highly recommended for complete protection.
References
https://github.com/n8n-io/n8n/security/advisories/GHSA-r4v6-9fqc-w5jr
