n8n, an open-source platform for workflow automation, recently addressed an important security vulnerability impacting its AI Agents feature. This flaw, identified as CVE-2026-59207, could allow unauthorized access to sensitive information, posing a risk to users of affected versions.
Understanding the Vulnerability
At its core, the vulnerability meant that n8n’s AI Agents feature wasn’t properly enforcing security rules around HTTP requests. Specifically, when a tool called an MCP (Managed Credential Provider) was configured to point to an external website, it failed to respect the “Allowed HTTP Request Domains” restrictions. This oversight meant that a user with even limited “use-only” access to a shared credential could bypass these security controls. As a result, they could potentially send the credential’s secret, such as an API key or other sensitive data, to an external server they controlled.
This kind of issue highlights the critical importance of robust credential management best practices in any workflow automation platform, especially those integrating AI capabilities.
CVE Details
- Product: n8n
- CVE ID: CVE-2026-59207
- Published Date: July 9, 2026
- Severity: Medium
- Status: Analyzed
Affected Products
The vulnerability impacts specific versions of the n8n platform. Users running the following versions are affected:
- n8n versions prior to 2.27.4
- n8n versions prior to 2.28.1
It is crucial for administrators and developers to verify their current n8n installation version to determine if they are at risk.
Current Status
The vulnerability (CVE-2026-59207) has been thoroughly analyzed by the n8n team. Patches addressing this issue have been released, and users are strongly encouraged to update their installations promptly.
Severity Level
The vulnerability has been assigned a CVSS score of 6.5, categorizing it as a Medium severity issue. This rating indicates that while exploitation might require specific conditions, the impact could be significant, primarily due to the potential for unauthorized information disclosure. Allowing a malicious actor to steal credentials could lead to further compromise of integrated systems and data.
Possible Solutions
The good news is that n8n has already released fixes for this vulnerability. To secure your n8n instance against CVE-2026-59207, you must upgrade to one of the patched versions:
- Upgrade to n8n version 2.27.4
- Upgrade to n8n version 2.28.1
Or any subsequent version that includes these fixes. It is always recommended to perform a backup before any major system updates and test the upgrade in a non-production environment first. Staying on top of workflow automation security updates is vital for maintaining a secure environment.
References
https://github.com/n8n-io/n8n/releases/tag/n8n%402.27.4
https://github.com/n8n-io/n8n/releases/tag/n8n%402.28.1
https://github.com/n8n-io/n8n/security/advisories/GHSA-h44j-f5r5-ph73
