Description
n8n is an open source workflow automation platform. Prior to 2.27.4 and from 2.28.0 prior to 2.28.1, n8n instances configured with more than one trusted token-exchange issuer resolved external identities to local accounts using only the JWT sub claim and ignored the iss claim, allowing an attacker with a valid token from one trusted issuer and a sub matching a victim under another issuer to authenticate as that victim. This issue is fixed in versions 2.27.4 and 2.28.1.
Affected products
n8n: n8n
References3
- github.com/n8n-io/n8n/security/advisories/GHSA-mq3m-f8x3-579w Vendor Advisory
- github.com/n8n-io/n8n/releases/tag/n8n%402.27.4 Release Notes
- github.com/n8n-io/n8n/releases/tag/n8n%402.28.1 Release Notes
Metrics
- CVSS 3.1
-
6.8
MEDIUM
Score source: NVD
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N - CVSS 4.0
-
7.6
HIGH
Score source: CNA
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X - EPSS — exploit probability
- 0% percentile: 19 · as of 15 November 2026
- CWE
- CWE-287CWE-346
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.