---
id: CVE-2026-59208
aliases:
  - GHSA-mq3m-f8x3-579w
title: >-
  n8n: Cross-Issuer Token Exchange Account Binding via Subject-Only Identity
  Resolution
summary: >-
  n8n: Cross-Issuer Token Exchange Account Binding via Subject-Only Identity
  Resolution
severity: high
cwe:
  - CWE-287
  - CWE-346
vendor: n8n
product: n8n
ecosystem: npm
affected:
  - 'n8n >= 2.28.0, < 2.28.1'
  - n8n < 2.27.4
patched:
  - n8n 2.28.1
  - n8n 2.27.4
published: '2026-07-22'
updated: '2026-07-22'
source: GHSA
sourceUrl: 'https://github.com/advisories/GHSA-mq3m-f8x3-579w'
references:
  - url: 'https://github.com/n8n-io/n8n/security/advisories/GHSA-mq3m-f8x3-579w'
  - url: 'https://nvd.nist.gov/vuln/detail/CVE-2026-59208'
  - url: 'https://github.com/n8n-io/n8n/releases/tag/n8n@2.27.4'
  - url: 'https://github.com/n8n-io/n8n/releases/tag/n8n@2.28.1'
  - url: 'https://github.com/advisories/GHSA-mq3m-f8x3-579w'
tags:
  - ghsa
  - npm
epss: 0.00265
epssPercentile: 0.16343
ingestedAt: '2026-07-22T22:06:57.473Z'
---

## Overview

## Impact
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.

## Patches
The issue has been fixed in n8n version 2.28.1. Users should upgrade to this version or later to remediate the vulnerability.

## Workarounds
If upgrading is not immediately possible, administrators should consider the following temporary mitigations:
- If multiple trusted issuers are not required, reduce the token exchange configuration to a single trusted issuer.
- Disable the token exchange feature entirely if it is not in active use.

These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

## Affected packages

- `n8n >= 2.28.0, < 2.28.1`
- `n8n < 2.27.4`

## Remediation

Upgrade to a patched release:

- `n8n 2.28.1`
- `n8n 2.27.4`