Loading vulnerability…
CVE-2026-59208 is an authentication flaw in n8n affecting versions prior to 2.27.4 and versions from 2.28.0 prior to 2.28.1. In deployments configured with more than one trusted token-exchange issuer, n8n resolved external identities to local accounts using only the JWT subject claim and failed to incorporate the issuer claim during account mapping. As a result, a token legitimately issued by one trusted issuer could be accepted as belonging to a local account associated with a different trusted issuer if both identities shared the same subject value. This creates an issuer-confusion condition that can allow cross-issuer account impersonation.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
9 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.