n8n is vulnerable to Improper Authorization through its `/stop` endpoint
SummaryAn 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.ImpactThis 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.PatchesThe 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.WorkaroundsTo mitigate this issue without upgrading:Restrict access to the `/rest/executions/:id/stop` endpoint via reverse proxy or API gateway.