GHSA-664H-GPGQ-H6XX

Workarounds

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

• Restrict project membership to fully trusted users only.
• Avoid granting viewer access to projects containing sensitive workflows.

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

Three mutating endpoints in the evaluation test runs controller authorized state-changing actions using workflow:read instead of the action-appropriate workflow:execute scope. An authenticated user with project:viewer role on a project could start new evaluation test runs, cancel in-flight runs, and delete run records for workflows they only had read access to.

This issue only affects instances with Advanced Permissions (Enterprise/Cloud) where projects and viewer roles are in use.

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

GHSA-664H-GPGQ-H6XX has a CVSS score of 5.4 (Medium). 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.55, 2.26.2, 2.25.7); upgrading removes the vulnerable code path.

Kodem intelligence

The issue has been fixed in n8n versions 1.123.55, 2.25.7, and 2.26.2. Users should upgrade to one of these versions or later to remediate the vulnerability.

1. What is GHSA-664H-GPGQ-H6XX? GHSA-664H-GPGQ-H6XX is a medium-severity incorrect authorization vulnerability in n8n (npm), affecting versions < 1.123.55. It is fixed in 1.123.55, 2.26.2, 2.25.7. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
2. How severe is GHSA-664H-GPGQ-H6XX? GHSA-664H-GPGQ-H6XX has a CVSS score of 5.4 (Medium). 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 GHSA-664H-GPGQ-H6XX? n8n (npm) versions < 1.123.55 is affected.
4. Is there a fix for GHSA-664H-GPGQ-H6XX? Yes. GHSA-664H-GPGQ-H6XX is fixed in 1.123.55, 2.26.2, 2.25.7. Upgrade to this version or later.
5. Is GHSA-664H-GPGQ-H6XX exploitable, and should I be worried? Whether GHSA-664H-GPGQ-H6XX 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 GHSA-664H-GPGQ-H6XX 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 GHSA-664H-GPGQ-H6XX?
   • Upgrade n8n to 1.123.55 or later
   • Upgrade n8n to 2.26.2 or later
   • Upgrade n8n to 2.25.7 or later