n8n: Cross-Tenant Credential Takeover via Dynamic Credentials EE Endpoints
n8n
- Severity
- Critical, CVSS 9.9
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L
- Record
- CVE-2026-54305
- Affects
- n8n
- Known exploited
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Published
- Record first published by the source
- June 23, 2026
- Source last modified
- October 25, 2026
Description
n8n is an open source workflow automation platform. Prior to 1.123.55, 2.25.7, and 2.26.2, three EE endpoints used by the Dynamic Credentials feature accepted any authenticated n8n session without performing per-resource ownership or scope checks on the target workflow or credential. An authenticated user with no project membership or credential sharing relationship could enumerate credential identifiers, names, and types referenced by any private workflow in the instance, initiate an OAuth authorization flow against another user's credential to overwrite its stored tokens with tokens bound to an account they control, or revoke another user's stored credential tokens entirely. Workflows relying on a hijacked credential would subsequently execute under the attacker's OAuth identity, enabling data exfiltration to attacker-controlled external services and persistent takeover of integrations. Token revocation would break affected workflows. This vulnerability is fixed in 1.123.55, 2.25.7, and 2.26.2.
Description quoted from the NVD record.
Who is affected
n8n, a tool for connecting apps and automating tasks, has a flaw in its Dynamic Credentials feature, which handles the saved logins workflows use to reach other services. This flaw affects versions before 1.123.55, 2.25.7 and 2.26.2. Anyone with any n8n login, without access to a project, could see which saved logins other people's private workflows use, swap another user's saved login for one tied to an account they control, or cancel it. Workflows using a swapped login would then run as the attacker, letting them send your data to outside services and keep control of those connections. Canceled logins would break workflows. This flaw is rated Critical.
What to do
- If you or a staff member installed and run n8n yourselves, that person should update it to version 1.123.55, 2.25.7 or 2.26.2 (or later), choosing the one that matches the version line you are on.
- If an IT provider or vendor runs n8n for your organization, send them this advisory and ask when the update will be done.
- After the update, check that workflows using saved logins still run, because a login canceled through this flaw would stop them from working.
Analysis written from the source record as of October 25, 2026 and reviewed before publishing.