CVE-2025-52554

An authorization vulnerability was discovered in the /rest/executions/:id/stop endpoint of n8n. An authenticated user can stop workflow executions that they do not own or that have not been shared with them, leading to potential business disruption.

Workarounds

To mitigate this issue without upgrading:

• Restrict access to the /rest/executions/:id/stop endpoint via reverse proxy or API gateway.

This is an improper authorization vulnerability. While most API methods enforce user-scoped access to workflow execution IDs, the /stop endpoint fails to do so. An attacker can guess or enumerate execution IDs (which are sequential and partially exposed via verbose error messages) and terminate active workflows initiated by other users.

Who is impacted:

• Environments where multiple users with varying trust levels share access to the same n8n instance.
• All users running long-running or time-sensitive workflows (e.g., using the wait node).

An attacker with authenticated access can exploit this flaw to:

• Disrupt other users’ workflow executions.
• Cause denial of service for business-critical automations.

The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.

CVE-2025-52554 has a CVSS score of 4.3 (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.99.1); upgrading removes the vulnerable code path.

Kodem intelligence

The issue was addressed in https://github.com/n8n-io/n8n/pull/16405. Users should upgrade to version >= 1.99.1.

Users should upgrade to this version or later to ensure proper authorization checks are enforced before stopping workflow executions.

1. What is CVE-2025-52554? CVE-2025-52554 is a medium-severity missing authorization vulnerability in n8n (npm), affecting versions < 1.99.1. It is fixed in 1.99.1. The application does not perform an authorization check before performing a sensitive operation.
2. How severe is CVE-2025-52554? CVE-2025-52554 has a CVSS score of 4.3 (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 CVE-2025-52554? n8n (npm) versions < 1.99.1 is affected.
4. Is there a fix for CVE-2025-52554? Yes. CVE-2025-52554 is fixed in 1.99.1. Upgrade to this version or later.
5. Is CVE-2025-52554 exploitable, and should I be worried? Whether CVE-2025-52554 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-2025-52554 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-2025-52554? Upgrade n8n to 1.99.1 or later.