n8n is vulnerable to Improper Authorization through its `/stop` endpoint
Medium4.3CVE-2025-52554 · Published Jul 3, 2025
## Summary 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. ### Impact 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. ### Patches 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 aut...
Affected versions
| Package | Affected | Fixed in |
|---|---|---|
| n8n npm | < 1.99.1 | 1.99.1 |
Details and references
## Summary 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. ### Impact 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. ### Patches 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. ### Workarounds To mitigate this issue without upgrading: - Restrict access to the `/rest/executions/:id/stop` endpoint via reverse proxy or API gateway.
- CVSS 3.1
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
- Severity from
- GitHub (reviewed advisory)
- Weakness
- CWE-862
- Also known as
- CVE-2025-52554
More n8n advisories
All n8n| Date | Advisory | Severity | Fixed in |
|---|---|---|---|
| Sep 152025 | Stored XSS in n8n LangChain Chat Trigger Node via initialMessages Parameter | Medium4.1 | 1.107.0 |
| Aug 202025 | n8n symlink traversal vulnerability in "Read/Write File" node allows access to restricted files | Medium6.5 | 1.106.0 |
| Aug 192025 | Stored XSS in n8n Form Trigger allows Account Takeover via injected iframe and video/source | High8.7 | 1.98.2 |
| Jul 32025 | n8n Vulnerable to Denial of Service via Malformed Binary Data Requests | Medium4.9 | 1.99.0 |
| Jun 272025 | n8n allows open redirects via the /signin endpoint | Medium4.6 | 1.98.0 |
| Apr 282025 | n8n Vulnerable to Stored XSS through Attachments View Endpoint | Medium5.0 | 1.90.0 |