n8n before 2.32.1 (and before 2.31.5) is vulnerable to account takeover via the Token Exchange Embed Login feature. When a validly-signed incoming token was matched to a local account by its email claim, the service did not verify that the email claim was verified, nor that the trusted key's permitted role ceiling covered that account. As a result, anyone able to obtain a token accepted by a configured trusted key (for example, a trusted issuer emitting unverified email addresses) could authenticate as any existing user and gain full account control. This issue only affects instances where the embed login feature is enabled and at least one trusted key source is configured.
Fix
Patch, vendor advisory and mitigation references on NVD 1
- https://github.com/n8n-io/n8n/security/advisories/GHSA-8342-988q-86cr Mitigation, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 8.9 · n8nNVD modified 2026-10-23 19:10
Affected (CPE criteria) 2
cpe:2.3:a:n8n:n8n:*:*:*:*:*:node.js:*:*cpe:2.3:a:n8n:n8n:2.32.0:*:*:*:*:node.js:*:*
References 2
- https://github.com/n8n-io/n8n/security/advisories/GHSA-8342-988q-86cr Mitigation, Vendor Advisory
- https://www.vulncheck.com/advisories/n8n-before-authentication-bypass-via-token-exchange Third Party Advisory