Loading story…
A stored DOM-based cross-site scripting flaw tracked as CVE-2026-65592 affects the n8n workflow automation platform, allowing authenticated users with workflow creation or editing rights to plant a malicious URI in the Resource Locator component's cachedResultUrl field. The value is saved in workflow metadata and later passed to window.open() without validating the URL scheme, so a victim who opens the crafted workflow and clicks the external resource link can trigger attacker-controlled JavaScript in their browser.
The vulnerability affects n8n versions before 1.123.64, before 2.29.8, and before 2.30.1. Reports say the bug could enable session hijacking or abuse of n8n API access available to the victim user, and classify the issue as CWE-79 with network attackability, low attack complexity, low privileges required, and user interaction required. Recommended remediation is to upgrade to a fixed release and enforce strict scheme validation so only safe http and https URLs are accepted in cachedResultUrl.
See affected versions and whether adversaries are exploiting it.
1 event from the most recent confirmed update back to the earliest known activity.
A stored DOM-based cross-site scripting vulnerability affecting n8n was disclosed as CVE-2026-65592. The flaw involves the Resource Locator component passing a workflow-persisted cachedResultUrl value to window.open() without validating the URL scheme, enabling JavaScript execution when a victim interacts with a crafted link.
Vulnerabilities, threat actors, malware, products, organizations, breaches, and observables Mallory has linked to this story. Indicator values are masked here and available in full in the app.
Indicator values are masked on this page. See the values in Mallory Domains, IPs, hashes, and URLs are exportable to your SIEM.
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.
cvereports.com
Open sourcecvefeed.io
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 DOM-based XSS flaw tracked as **`CVE-2026-65597`** affects **n8n**'s HTML preview feature, where execution output is rendered into an iframe using `srcdoc` without a `sandbox` attribute. The weakness allows a sanitizer bypass and same-origin script execution in the editor context, enabling an attacker to trigger authenticated actions through a victim's active session. The issue affects **n8n before `1.123.64`**, **`2.x` before `2.29.8`**, and versions before **`2.30.1`**. An attacker with **`global:member`** privileges can create or modify a workflow so a malicious payload is stored in execution output and later executed when an administrator opens the HTML preview panel. Reports say the injected script can access the parent window, steal session data from `localStorage` or cookies, and exfiltrate it to an attacker-controlled server, effectively enabling session hijacking and API abuse. The vendor mitigated the flaw by sandboxing the iframe in the patched implementation.
Jul 23, 2026
A critical remote code execution vulnerability, tracked as CVE-2026-21877, has been identified in the n8n workflow automation platform. The flaw, rated CVSS 10.0, allows authenticated users to execute arbitrary code on affected n8n instances, posing a significant risk to environments where n8n is used to automate workflows with access to sensitive data, internal systems, and credentials. The vulnerability impacts n8n versions from 0.123.0 up to but not including 1.121.3, affecting both self-hosted and managed deployments. Exploitation requires authenticated access, and the vulnerability is linked to unsafe handling that can result in the execution of untrusted code. The issue has been addressed in n8n version 1.121.3 and later, and users are strongly advised to upgrade immediately to mitigate the risk. Additional recommendations include restricting workflow modification access to trusted administrators, blocking high-risk nodes at runtime, and reviewing audit logs for suspicious activity prior to patching. No public exploit details or proof-of-concept have been released as of the latest advisories. Organizations using n8n should prioritize patching and implement hardening measures to prevent potential compromise of their automation infrastructure.
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