CVE-2026-33663

Workarounds

If upgrading is not immediately possible, administrators should consider the following temporary mitigations:

• Restrict instance access to fully trusted users only.
• Audit credentials stored on the instance and rotate any generic HTTP credentials (httpBasicAuth, httpHeaderAuth, httpQueryAuth) that may have been exposed.

These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

An authenticated user with the global:member role could exploit chained authorization flaws in n8n's credential pipeline to steal plaintext secrets from generic HTTP credentials (httpBasicAuth, httpHeaderAuth, httpQueryAuth) belonging to other users on the same instance.

The attack abuses a name-based credential resolution path that does not enforce ownership or project scope, combined with a bypass in the credentials permission checker that causes generic HTTP credential types to be skipped during pre-execution validation. Together, these flaws allow a member-role user to resolve another user's credential ID and execute a workflow that decrypts and uses that credential without authorization.

Native integration credential types (e.g. slackApi, openAiApi, postgres) are not affected by this issue.

This vulnerability affects Community Edition only. Enterprise Edition has additional permission gates on workflow creation and execution that independently block this attack chain.

CVE-2026-33663 has a CVSS score of 9.9 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.123.27, 2.14.1, 2.13.3); upgrading removes the vulnerable code path.

Kodem intelligence

The issue has been fixed in n8n versions 1.123.27, 2.13.3, and 2.14.1. Users should upgrade to one of these versions or later to remediate the vulnerability.

1. What is CVE-2026-33663? CVE-2026-33663 is a high-severity security vulnerability in n8n (npm), affecting versions < 1.123.27. It is fixed in 1.123.27, 2.14.1, 2.13.3.
2. How severe is CVE-2026-33663? CVE-2026-33663 has a CVSS score of 9.9 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of n8n are affected by CVE-2026-33663? n8n (npm) versions < 1.123.27 is affected.
4. Is there a fix for CVE-2026-33663? Yes. CVE-2026-33663 is fixed in 1.123.27, 2.14.1, 2.13.3. Upgrade to this version or later.
5. Is CVE-2026-33663 exploitable, and should I be worried? Whether CVE-2026-33663 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-33663 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-33663?
   • Upgrade n8n to 1.123.27 or later
   • Upgrade n8n to 2.14.1 or later
   • Upgrade n8n to 2.13.3 or later