dbcve.org
N8nApplication

CVE-2026-59208

MEDIUM · 6.8 CVSS v3.1 Published 2026-07-09
Fix available
A fix is available. Upgrade to 2.27.4 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable Zero-click 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

In the news

Third-party coverage
Trending covered by 1 outlet this week · latest 3d ago

Surfaced from public web coverage — external links open in a new tab.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In n8n instances configured with multiple trusted token-exchange issuers, external identity resolution used only the JWT sub claim and ignored the iss claim. This allowed attackers with valid tokens from one trusted issuer to authenticate as victims whose sub claim matched, if those victims existed under a different trusted issuer.

MitigationUpgrade n8n to version 2.27.4 or 2.28.1. Until then, ensure only a single token-exchange issuer is configured, or implement additional issuer validation at the identity provider level.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
N8nApplication
Affected:< 2.27.4= 2.28.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed n8n version
    Run `n8n --version` or check the version in your package.json/requirements file
    Affected if Version is below 2.27.4 or exactly 2.28.0 (versions 2.28.1 and above are not affected)
  2. Verify multiple token-exchange issuers are configured
    Review n8n environment variables or configuration for `N8N_AUTH_EXCHANGE_KEYS` or multiple issuer URLs in your identity provider settings
    Affected if More than one trusted issuer is configured in the token-exchange settings
  3. Confirm external identity provider authentication is enabled
    Check if `N8N_AUTH_EXCHANGE_KEYS` or similar SSO/SAML/OIDC configuration is active in your n8n environment configuration
    Affected if External token-exchange/SSO authentication is enabled and accepting tokens from multiple issuers
  4. Review existing user accounts for sub claim collisions
    Audit user accounts created via external identity providers, looking for users with identical sub claims but different issuers
    Affected if Multiple users exist with the same sub claim value originating from different trusted issuers

You are affected if your n8n version is vulnerable AND you have multiple token-exchange issuers configured AND external identity authentication is enabled, creating a scenario where a token from one issuer could impersonate a user with a matching sub claim under a different issuer.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.27.4 or later
Fixed in 2.27.4
Interim mitigation

Upgrade n8n to version 2.27.4 or 2.28.1. Until then, ensure only a single token-exchange issuer is configured, or implement additional issuer validation at the identity provider level.

Recommended fix High confidence

Upgrade to n8n version 2.27.4 (for versions < 2.27.4) or 2.28.1 (for version 2.28.0)

  1. 1. Identify the current n8n version by checking the instance or deployment configuration
  2. 2. If running a version < 2.27.4, upgrade to version 2.27.4
  3. 3. If running version 2.28.0, upgrade to version 2.28.1
  4. 4. Verify the upgrade was successful by checking the n8n version after restart
  5. 5. If using multiple trusted token-exchange issuers, verify the authentication configuration still works correctly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in N8n Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,472.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-59208 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-59208 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data