CVE-2026-59208: n8n Cross-Issuer Token Exchange Account Binding Vulnerability

HIGH
Advisory Identifier: GHSA-mq3m-f8x3-579w
CWE-287 CWE-346
Published
Advisory Summary

CVE-2026-59208 is a HIGH cross-issuer token exchange account binding vulnerability (CWE-287: Improper Authentication) affecting n8n libraries in the npm ecosystem. The issue involves cross-issuer token exchange account binding via subject-only identity resolution. Remediation is available by upgrading affected packages to version 2.28.1, 2.27.4.

CVE-2026-59208 at a Glance

CVE Identifier CVE-2026-59208
GHSA Identifier GHSA-mq3m-f8x3-579w
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-287: Improper Authentication
Affected Product n8n
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2026-59208

To remediate this vulnerability, upgrade all affected n8n dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

n8n fixed: 2.28.1
npm install n8n@2.28.1
n8n fixed: 2.27.4
npm install n8n@2.27.4
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls n8n

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-59208, inspect your project dependencies using npm:

npm ls n8n

Analyze the terminal output to locate any version of n8n in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.28.1), your application is affected.

Note: The npm ls n8n command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-287: Improper Authentication, where when an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. In n8n, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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

CVE-2026-59208 Affected n8n Versions

2 component(s)
Fixed Versions:
2.28.12.27.4
Product / Package Ecosystem Affected Versions Fixed Version
n8n
npm
≥ 2.28.0
< 2.28.1
2.28.1
n8n
npm
< 2.27.4
2.27.4

References

Frequently Asked Questions

What is CVE-2026-59208?
CVE-2026-59208 is a security vulnerability in n8n involving Cross-Issuer Token Exchange Account Binding via Subject-Only Identity Resolution under CWE-287: Improper Authentication.
Which n8n versions are affected?
Affected versions include releases prior to 2.28.1, 2.27.4 across affected packages: n8n.
What version fixes CVE-2026-59208?
Upgrading to 2.28.1, 2.27.4 (or the latest patched release for your respective branch) resolves the vulnerability.
Is n8n affected?
Yes, n8n is affected in releases prior to 2.28.1, 2.27.4. Upgrade your dependency to 2.28.1, 2.27.4 or later.
What CWE is associated with CVE-2026-59208?
CVE-2026-59208 is classified under CWE-287: Improper Authentication (When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.).
How can I check npm dependencies for CVE-2026-59208?
Run the dependency tree command: 'npm ls n8n'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-mq3m-f8x3-579w",
  "modified" : "2026-07-22T21:59:15Z",
  "published" : "2026-07-22T21:59:15Z",
  "aliases" : [ "CVE-2026-59208" ],
  "summary" : "n8n: Cross-Issuer Token Exchange Account Binding via Subject-Only Identity Resolution",
  "details" : "## Impact\nWhen 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.\n\nAn 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.\n\nThis issue only affects instances where the token exchange feature is enabled and more than one trusted external issuer is configured.\n\n## Patches\nThe issue has been fixed in n8n version 2.28.1. Users should upgrade to this version or later to remediate the vulnerability.\n\n## Workarounds\nIf upgrading is not immediately possible, administrators should consider the following temporary mitigations:\n- If multiple trusted issuers are not required, reduce the token exchange configuration to a single trusted issuer.\n- Disable the token exchange feature entirely if it is not in active use.\n\nThese workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "n8n"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.28.0"
      }, {
        "fixed" : "2.28.1"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "n8n"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.27.4"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/n8n-io/n8n/security/advisories/GHSA-mq3m-f8x3-579w"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-59208"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/n8n-io/n8n"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/n8n-io/n8n/releases/tag/n8n@2.27.4"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/n8n-io/n8n/releases/tag/n8n@2.28.1"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-287", "CWE-346" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-07-22T21:59:15Z",
    "nvd_published_at" : "2026-07-09T16:16:46Z"
  }
}