GHSA-gq57-v332-7666
MEDIUMn8n is vulnerable to Improper Authorization through its `/stop` endpoint
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
n8nnpmDescription
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
waitnode).
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/stopendpoint via reverse proxy or API gateway.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | n8n | all versions | 1.99.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for n8n. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update n8n to 1.99.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gq57-v332-7666 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-gq57-v332-7666 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-gq57-v332-7666. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-gq57-v332-7666 in your dependencies?
O3 detects GHSA-gq57-v332-7666 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.