Loading story…
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.
See affected versions and whether adversaries are exploiting it.
1 event from the most recent confirmed update back to the earliest known activity.
A high-severity privilege escalation vulnerability, CVE-2026-65595, was publicly disclosed affecting n8n versions before 2.30.1 and before 2.29.8 on a separate branch. The flaw allows a low-privileged user with a valid external JWT to gain administrator-level Public API access, and in some configurations may lead to remote code execution.
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.
2 references tracked. Mallory keeps watching after this page renders.
cvefeed.io
Open sourcecvereports.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.
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.
Jul 17, 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
A critical `CVSS 10.0` vulnerability in locally deployed n8n automation instances, tracked as `CVE-2026-21858` and dubbed **Ni8mare**, enables unauthenticated attackers to read arbitrary local files, bypass authentication, and execute commands. The flaw stems from Content-Type confusion in webhook parsing: the Form Webhook node can invoke file handling without requiring `multipart/form-data`, allowing attacker-controlled file paths to be copied into persistent storage. Researchers estimate that roughly 100,000 internet-exposed servers may be affected. Attackers can use the file-read primitive to obtain sensitive files, including `/etc/passwd`, the local SQLite database, and n8n configuration secrets. With database contents and the instance secret, they can forge an `n8n-auth` session cookie, gain administrator access, and create workflows using the **Execute Command** node for remote code execution. Organizations running self-hosted n8n should upgrade to version `1.121.0` or later; no official workaround is available.
Sep 18, 2026