Skip to main content
Mallory
HighVulnerability

CVE-2026-59208: Cross-Issuer Account Impersonation in n8n Enterprise Token Exchange

Published Jul 9, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.6High · v4
EPSS0.27%19th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
N8n
IdentifiersCVE-2026-59208CWE-287 · Improper Authentication

CVE-2026-59208 is an improper authentication and identity-binding vulnerability in n8n Enterprise deployments that use the token exchange feature with multiple trusted external JWT issuers. In affected versions, n8n resolved an external identity to a local account using only the JWT subject claim (sub) and failed to bind that identity to the issuer claim (iss). Because JWT subject values are only unique within the context of an issuer, two different trusted issuers can legitimately produce the same sub value. Under those conditions, a cryptographically valid token from one trusted issuer could be incorrectly mapped to a local user associated with another trusted issuer. The flaw affects versions prior to 2.27.4 on the 2.27 branch and version 2.28.0, and was fixed in 2.27.4 and 2.28.1.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows cross-issuer user impersonation. An attacker who possesses a valid token from one trusted issuer can be authenticated as another user whose account is associated with a different trusted issuer if the sub values collide. This can grant the attacker an authenticated session as the victim user, inheriting that user’s n8n permissions and access to workflows, credentials, and connected business systems reachable through the impersonated account. The vulnerability does not require the victim’s password and does not depend on bypassing JWT signature verification; it occurs during post-validation identity mapping.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure by configuring only a single trusted token-exchange issuer where operationally feasible, or disable the token exchange feature entirely if it is not required. Restrict access to the affected n8n instance until remediation is complete, avoid adding additional trusted issuers, and review multi-issuer deployments for accounts that may share the same subject value across issuers.

Remediation

Patch, then assume compromise.

Upgrade n8n to a fixed release. The first patched versions are 2.27.4 on the 2.27 branch and 2.28.1 on the 2.28 branch. After upgrading, validate that token exchange identity mapping correctly binds users by both issuer and subject across all configured trusted issuers, and review trusted issuer configuration to ensure only necessary issuers remain enabled.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
N8nN8napplication
FAQ

Frequently asked questions

Is CVE-2026-59208 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-59208 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-59208?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-59208.
Is there a patch for CVE-2026-59208?
Upgrade n8n to a fixed release. The first patched versions are 2.27.4 on the 2.27 branch and 2.28.1 on the 2.28 branch.
What products are affected by CVE-2026-59208?
N8n.
How severe is CVE-2026-59208?
CVE-2026-59208 has a CVSS v4 score of 7.6 (High) and an EPSS score of 0.27% (19th percentile) as of Sep 25, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity19Community discussion across Reddit, Mastodon, and other social sources.