Skip to main content
CVE-2025-52554VulnerabilityPublished

CVE-2025-52554: n8n · Missing Authorization

Affects n8nSource CVE Database V5

0

Not known to be exploited · CVSS 4.9 Medium : upgrade to 1.99.1 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score
4.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.99.1
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Upgrade n8n-io/n8n to 1.99.1.

Affected software

ProductAffectedFixed in
GitHubn8n-io/n8npkg:github/n8n-io/n8nOther threatsAffected
  • <1.99.1
Fixed in
  • 1.99.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

The primary mitigation is to upgrade n8n to version 1.99.1 or later, where the authorization checks for the /rest/executions/:id/stop endpoint have been properly implemented. Until an upgrade is feasible, organizations should implement access controls at the network level by restricting access to the vulnerable endpoint using a reverse proxy or API gateway. This can include IP whitelisting, authentication enforcement, or endpoint filtering to ensure only authorized users or systems can invoke the stop execution API. Additionally, organizations should audit user privileges within n8n to ensure that only trusted users have authenticated access, minimizing the risk of exploitation by low-privilege users. Monitoring and alerting on unusual workflow stoppage events can help detect potential exploitation attempts. Finally, reviewing and hardening the overall API security posture of n8n deployments is recommended to prevent similar authorization issues.

Description

n8n is a workflow automation platform. Prior to version 1.99.1, 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. This issue has been patched in version 1.99.1. A workaround involves restricting access to the /rest/executions/:id/stop endpoint via reverse proxy or API gateway.

References

Community reviews

Loading reviews…