GHSA-H3JJ-5F3V-3685

Workarounds

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

• Restrict workflow sharing to fully trusted users only.
• Restrict network access to the n8n Public API to trusted users only.

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

The Public API endpoint for retrying executions authorized access using workflow:read rather than workflow:execute. An authenticated user with read-only access to a shared workflow could use the Public API to retry executions of that workflow, bypassing the intended permission boundary between read and execute access.

This issue affects instances where workflows are shared with other users or across projects.

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-H3JJ-5F3V-3685 has a CVSS score of 6.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 (2.26.2, 2.25.7); upgrading removes the vulnerable code path.

Kodem intelligence

The issue has been fixed in n8n versions 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-H3JJ-5F3V-3685? GHSA-H3JJ-5F3V-3685 is a medium-severity incorrect authorization vulnerability in n8n (npm), affecting versions >= 2.26.0, < 2.26.2. It is fixed in 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-H3JJ-5F3V-3685? GHSA-H3JJ-5F3V-3685 has a CVSS score of 6.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-H3JJ-5F3V-3685? n8n (npm) versions >= 2.26.0, < 2.26.2 is affected.
4. Is there a fix for GHSA-H3JJ-5F3V-3685? Yes. GHSA-H3JJ-5F3V-3685 is fixed in 2.26.2, 2.25.7. Upgrade to this version or later.
5. Is GHSA-H3JJ-5F3V-3685 exploitable, and should I be worried? Whether GHSA-H3JJ-5F3V-3685 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-H3JJ-5F3V-3685 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-H3JJ-5F3V-3685?
   • Upgrade n8n to 2.26.2 or later
   • Upgrade n8n to 2.25.7 or later