The vulnerability in n8n allows unauthenticated actors to trigger workflow execution by ignoring the unguessable server-generated identifier and matching only on the request path. This authentication bypass permits execution of any workflow within any project, potentially leading to remote code execution or credential leakage under the project’s account. The weakness aligns with CWE‑288, representing an authorization bypass through user‑controlled data. The impact includes loss of confidentiality, integrity, and availability of the project and any underlying infrastructure accessed by the workflow.

The flaw affects n8n versions prior to 1.123.83 for the 1.x line, and all 2.x releases prior to 2.41.4 for the 2.x line, as well as 2.42.x releases before 2.42.1. Any deployments using these versions are susceptible to unauthorized workflow execution. The product is distributed as the open‑source n8n workflow automation tool, and the vendor is n8n‑io.

The CVSS score of 6.3 indicates medium severity, and the EPSS score is not available, implying that the exploit probability is undetermined but potentially non‑negligible. The vulnerability is not listed in CISA KEV, suggesting no confirmed widespread exploitation as of now. Nevertheless, the attack surface is exposed on publicly reachable webhook endpoints, and any external actor with network access to those endpoints can exploit the flaw immediately by sending crafted requests without authentication. This makes the risk high for environments with exposed webhook URLs and could result in full compromise of project credentials if utilized by an attacker.