CVE-2026-59208: CWE-287: Improper Authentication in n8n-io n8n
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.
AI Analysis
Technical Summary
The vulnerability in n8n affects instances configured with more than one trusted token-exchange issuer. The authentication mechanism incorrectly resolves external identities by validating only the JWT sub claim, disregarding the issuer claim. This improper authentication (CWE-287) enables an attacker possessing a valid token from one trusted issuer to authenticate as a victim user under a different issuer if the sub claim matches the victim's identifier. The flaw is present in versions prior to 2.27.4 and versions from 2.28.0 up to but excluding 2.28.1. The vendor fixed the issue in versions 2.27.4 and 2.28.1.
Potential Impact
An attacker with a valid token from one trusted issuer can impersonate another user from a different trusted issuer by exploiting the improper validation of JWT claims. This can lead to unauthorized access to the victim's account and potentially sensitive workflows or data within the n8n platform. The vulnerability has a CVSS 4.0 score of 7.6 (high severity), indicating a significant risk if exploited.
Mitigation Recommendations
Upgrade affected n8n instances to version 2.27.4 or 2.28.1 or later, where the authentication logic correctly validates both the sub and iss claims in JWT tokens. Patch status is confirmed by the vendor advisory indicating these versions fix the issue. No other mitigations are specified.
CVE-2026-59208: CWE-287: Improper Authentication in n8n-io n8n
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.
CVSS v4.0
Score 7.6high
Affected software
pkg:github/n8n-io/n8nRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in n8n affects instances configured with more than one trusted token-exchange issuer. The authentication mechanism incorrectly resolves external identities by validating only the JWT sub claim, disregarding the issuer claim. This improper authentication (CWE-287) enables an attacker possessing a valid token from one trusted issuer to authenticate as a victim user under a different issuer if the sub claim matches the victim's identifier. The flaw is present in versions prior to 2.27.4 and versions from 2.28.0 up to but excluding 2.28.1. The vendor fixed the issue in versions 2.27.4 and 2.28.1.
Potential Impact
An attacker with a valid token from one trusted issuer can impersonate another user from a different trusted issuer by exploiting the improper validation of JWT claims. This can lead to unauthorized access to the victim's account and potentially sensitive workflows or data within the n8n platform. The vulnerability has a CVSS 4.0 score of 7.6 (high severity), indicating a significant risk if exploited.
Mitigation Recommendations
Upgrade affected n8n instances to version 2.27.4 or 2.28.1 or later, where the authentication logic correctly validates both the sub and iss claims in JWT tokens. Patch status is confirmed by the vendor advisory indicating these versions fix the issue. No other mitigations are specified.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-07-02T21:05:02.924Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a4fbf4868715ace439fdda7
Added to database: 07/09/2026, 15:33:28 UTC
Last enriched: 07/17/2026, 09:31:15 UTC
Last updated: 08/23/2026, 10:52:10 UTC
Views: 150
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.