CVE-2026-56778
mediumpriority · track · 0OT risk · elevatedEPSS 0.003 · 22 %ileDEEUUSEPSS · scored 2026-10-27
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.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · low–medium · 1.3–6.4
ssvc
A stakeholder decision — act, attend, or track — from exploitation and impact.
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (12)
Products and version ranges known to be affected.
advisories (2)
Vendor and ecosystem advisories describing this.
- WID-SEC-W-2026-1875n8n: Mehrere SchwachstellenDeutsch2026-06-10csaf · cert_bundDE
Ein Angreifer kann mehrere Schwachstellen in n8n ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, SQL-Injection- und Cross-Site-Scripting-Angriffe durchzuführen, Daten zu manipulieren, einen Denial-of-Service-Zustand zu verursachen oder vertrauliche Informationen offenzulegen, was weitere Angriffe einschließlich einer Rechteausweitung ermöglichen kann.
- GHSA-h3jj-5f3v-3685n8n: Public API Execution Retry Authorization Bypass2026-06-16ghsa · osvUS
## Impact The Public API endpoint for retrying executions authorized access using `workflow:read` rather than `workflow:execute`. An authenticated user with read-only access to a shared workflow could use the Public API to retry executions of that workflow, bypassing the intended permission boundary between read and execute access. This issue affects instances where workflows are shared with other users or across projects. ## Patches The issue has been fixed in n8n versions 2.25.7, and 2.26.2. Users should upgrade to one of these versions or later to remediate the vulnerability. ## Workarounds If upgrading is not immediately possible, administrators should consider the following temporary mitigations: - Restrict workflow sharing to fully trusted users only. - Restrict network access to the n8n Public API to trusted users only. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
also known as (3)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (6)
External citations — patches, advisories, analysis.
- https://github.com/n8n-io/n8n/security/advisories/GHSA-h3jj-5f3v-3685cnnvd
- https://www.vulncheck.com/advisories/n8n-authorization-bypass-in-public-api-execution-retry-endpointcnnvd
- https://github.com/n8n-io/n8n/security/advisories/GHSA-h3jj-5f3v-3685enisa_euvd
- https://www.vulncheck.com/advisories/n8n-authorization-bypass-in-public-api-execution-retry-endpointenisa_euvd
- https://github.com/n8n-io/n8n/security/advisories/GHSA-h3jj-5f3v-3685MitigationVendor Advisorynvd
- https://www.vulncheck.com/advisories/n8n-authorization-bypass-in-public-api-execution-retry-endpointThird Party Advisorynvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan