| Package | Affected versions | Patched versions |
|---|---|---|
| n8n | = 2.28.0< 2.27.4 | 2.27.4 |
| n8n | ≥ 2.28.0, < 2.28.1< 2.27.4 | 2.28.12.27.4 |
When an n8n instance is configured with more than one trusted token-exchange issuer, external identities are resolved to local accounts using only the JWT sub claim, ignoring the issuer (iss). As a result, two different issuers that emit the same subject value map to the same local account.
An attacker who can obtain a valid token from one trusted issuer with a sub matching a victim registered under a different issuer can authenticate as that victim and access their account.
This issue only affects instances where the token exchange feature is enabled and more than one trusted external issuer is configured.
The issue has been fixed in n8n version 2.28.1. Users should upgrade to this version or later to remediate the vulnerability.
If upgrading is not immediately possible, administrators should consider the following temporary mitigations:
These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free