Loading story…
n8n disclosed CVE-2026-59208, an improper authentication flaw in the Enterprise token exchange feature that can let a user with a valid JWT from one trusted external issuer be logged into another user’s local account. The bug stems from n8n matching identities only on the JWT sub claim while ignoring the iss claim, creating a cross-issuer collision risk when multiple trusted issuers are configured and subject values overlap. Successful exploitation could give an attacker the victim’s n8n permissions, including access to workflows, stored credentials, and connected business systems.
The issue affects Enterprise deployments using token exchange with at least two trusted external issuers configured, including versions earlier than 2.27.4 on the 2.27 branch and 2.28.0 on the 2.28 branch. n8n fixed the flaw in 2.27.4 and 2.28.1 on June 24, and public reporting said there was no confirmed active exploitation or public proof-of-concept as of July 16. Organizations are advised to upgrade immediately, review trusted issuer settings, validate issuer-to-user binding after patching, and, if patching is delayed, reduce configurations to a single issuer or disable token exchange temporarily.
See affected versions and whether adversaries are exploiting it.
3 events from the most recent confirmed update back to the earliest known activity.
As of this date, reporting stated there was no confirmed active exploitation of CVE-2026-59208 and no public proof-of-concept available. CISA was also noted as having no known exploitation recorded.
The authentication flaw was publicly disclosed as CVE-2026-59208. Public reporting described how a valid token from one trusted issuer could be mapped to a user from another issuer when subject values collided.
n8n fixed the cross-issuer impersonation flaw in its Enterprise token exchange feature by releasing versions 2.27.4 and 2.28.1. The issue affected deployments that trusted multiple external JWT issuers and matched users only on the JWT subject claim.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
3 references tracked. Mallory keeps watching after this page renders.
malware.news
Open sourcesocradar.io
Open sourcethehackernews.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
A high-severity flaw tracked as **CVE-2026-65595** affects **n8n** versions before **2.30.1** and, on a separate branch, before **2.29.8**. The vulnerability stems from the Token Exchange module assigning **all Public API scopes** to JWT-derived access tokens after validating an external JWT from a trusted issuer, allowing a low-privileged user to gain administrator-level Public API access when both **Token Exchange** and **Public API** are enabled. The issue is rated **CVSS v4.0 8.9** and classified as **`CWE-269` Improper Privilege Management**. Successful exploitation can let an attacker perform admin-only actions including creating or deleting users, escalating roles, modifying workflows, reading database credentials stored in connection configurations, and exporting sensitive system data. In deployments that also allow installation of unverified Community Packages, the compromise can be extended to **remote code execution** on the n8n host, creating a path to full takeover of the automation platform and its underlying server.
Jul 23, 2026
n8n published security advisories for multiple supported release branches after disclosure of several vulnerabilities, including a critical flaw tracked as **`CVE-2026-56348`**. The CVE affects versions before **`2.20.0`** and allows an authenticated user to abuse the **`POST /rest/dynamic-node-parameters/options`** endpoint to bypass **Allowed HTTP Request Domains** restrictions, causing the server to send credential-bearing HTTP requests to unauthorized hosts and potentially exfiltrate sensitive authentication data. The issue is remotely exploitable and impacts environments where users can access affected dynamic node functionality. The broader advisory set also covers additional n8n weaknesses in releases prior to **`2.28.1`**, **`2.27.4`**, and **`1.123.61`**, including another Allowed HTTP Request Domains bypass through the **AI Agents MCP Connector**, prototype pollution via workflow credentials that can lead to unauthenticated user and project enumeration, cross-issuer token exchange account binding caused by subject-only identity resolution, and a shared credential header leak through HTTP request pagination expressions. The Canadian Centre for Cyber Security urged administrators to review the advisories, upgrade to the patched versions, restrict access to exposed endpoints where possible, and monitor for unauthorized outbound requests that could indicate credential leakage.
Jun 29, 2026
A **critical remote code execution** issue in the *n8n* open-source workflow automation platform, tracked as **CVE-2026-25049** (also published as **GHSA-6cqr-8cfr-67f8**), allows an **authenticated** user with permission to create or modify workflows to escape n8n’s expression sandbox and execute arbitrary system commands on the underlying host. The flaw stems from **insufficient input sanitization/weak sandboxing** in n8n’s expression evaluation (server-side JavaScript) and was identified during follow-up analysis after an earlier critical n8n vulnerability (**CVE-2025-68613**) was patched; researchers report the new issue effectively **bypasses prior mitigations**. Reporting indicates exploitation can lead to **full compromise** of the n8n instance, including access to the filesystem and the ability to **steal stored credentials and secrets** (e.g., API keys, OAuth tokens) and sensitive configuration, with potential for **pivoting** into connected internal services and cloud accounts in multi-tenant deployments. Public reporting also notes **public exploits** are available. n8n maintainers state the issue is patched, and affected organizations should upgrade to fixed releases (**1.123.17** and **2.5.2**), as versions **prior to 1.123.17 and 2.5.2** are impacted.
Jun 29, 2026