n8n Token Exchange Flaw Could Let Attackers Log In as Users From Another Issuer
Summary: n8n's Enterprise token-exchange feature matched incoming JWTs to local accounts on the sub claim alone and ignored iss, so a valid token from one trusted issuer could log in as a user belonging to another; the fix shipped June 24 and the CVE, tracked as CVE-2026-59208, went public July 9. The flaw affects releases below 2.27.4 and version 2.28.0, fixed in 2.27.4 and 2.28.1, and reaches an instance only when token exchange is enabled and at least two external issuers are trusted.
Bottom line: GitHub as CNA scored it 7.6 high on CVSS 4.0 while NVD put it at 6.8 medium on CVSS 3.1, and CISA's July 13 SSVC assessment recorded exploitation as none - so the severity you inherit depends on which score your process reads. Neither the 2.27.4 nor the 2.28.1 changelog mentions the identity fix, which means an upgrade decision driven by release notes would have missed it.
Read the original at The Hacker News ↗
- Topics
- Vulnerabilities & Patching
- Mentions
- CVE-2026-54305CVE-2026-59208
- Related
- ⚡ Weekly Recap: Word Press RCE, Sonic Wall 0-Days, AI Service Attacks, Share Point 0-Day and More Cyber Risks ·Attackers Exploit UnrealIRCd Flaw That Enables Server-Level Command Injection Cyber Risks · Nov 14, 2026U.S. CISA adds Check Point and UnrealIRCd flaws to its Known Exploited Vulnerabilities catalog Cyber Risks · Nov 14, 2026