Advisory

GHSA-mq3m-f8x3-579w

Also known as: CVE-2026-59208

Summary

n8n: Cross-Issuer Token Exchange Account Binding via Subject-Only Identity Resolution

Details

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.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2026-07-22 21:59 UTC
Modified
2026-07-22 22:16 UTC

Affected packages and fixes

n8n

npm · All systems

Affected

  • introduced 2.28.0, fixed 2.28.1 (semver)

Fixed versions

2.28.1

Fix

n8n

npm · All systems

Affected

  • introduced 0, fixed 2.27.4 (semver)

Fixed versions

2.27.4

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences