| Component | n8n |
| Severity | medium (CVSS 6.4) |
| CVSS vector | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N |
| Published (NVD) | 2026-07-08 |
| Affected versions | n8n < 2.25.7 n8n >= 2.26.0, < 2.26.2 |
| Fixed in | 2.25.7, 2.26.2 |
| Weakness | CWE-863 |
| CISA KEV | not listed |
NVD description
n8n before 2.25.7 and 2.26.x before 2.26.2 contains an authorization bypass in the Public API execution retry endpoint, which authorizes access using the workflow:read scope instead of workflow:execute. An authenticated user with read-only access to a shared workflow can use the Public API to retry executions of that workflow, bypassing the intended permission boundary between read and execute access. This affects instances where workflows are shared with other users or across projects.
What to do
- Upgrade n8n to
2.25.7or later (or the patched release of your branch: 2.26.2). - Do not expose the component's API or UI to the internet without authentication in front of it.
Sources
- NVD: CVE-2026-56778
- https://github.com/n8n-io/n8n/security/advisories/GHSA-h3jj-5f3v-3685
- https://www.vulncheck.com/advisories/n8n-authorization-bypass-in-public-api-execution-retry-endpoint
Read more
Other n8n CVEs
n8n versions before 1.123.80 contain a credential tampering vulnerability where duplicate node IDs bypass the workflow credential tamper gua...
n8n versions before 1.123.80, from 2.0.0 before 2.39.6, and from 2.40.0 before 2.40.1 contain a stored DOM cross-site scripting vulnerabilit...
n8n versions before 1.123.80, from 2.0.0 before 2.39.6, and from 2.40.0 before 2.40.1 contain a path traversal vulnerability in the Supabase...
n8n versions before 2.39.6 and 2.40.0 before 2.40.1 fail to validate credential ownership during inline agent node-tool introspection. Attac...
n8n versions before 1.123.80, from 2.0.0 before 2.39.6, and from 2.40.0 before 2.40.1 contain a filter injection vulnerability in the Supaba...
n8n versions before 1.123.80, from 2.0.0 before 2.39.6, and from 2.40.0 before 2.40.1 contain a NoSQL injection vulnerability in the MongoDB...