lowAgent ThreatOther

n8n Resource Locator Stored DOM XSS via cachedResultUrl (Withdrawn Duplicate Advisory)

First seen Jul 22, 2026 · Updated Jul 22, 2026

duplicate-advisoryxssn8nworkflow-automationjavascript-uriwithdrawnSurface: Human InterfacePropagation: None

This advisory has been officially withdrawn by GitHub as a duplicate of GHSA-9wcp-9r3j-383q, which should be consulted instead. The underlying issue is a stored DOM XSS in n8n's Resource Locator component (a workflow automation tool, not an AI agent framework per se), where a malicious javascript: URI in a persisted field can execute when a victim interacts with a crafted workflow. Severity is marked low here because this specific record carries no independent, actionable content beyond a pointer to another advisory.

Technical Analysis

n8n persists a cachedResultUrl value as part of Resource Locator workflow data and later passes it directly to window.open() without validating the URI scheme. An attacker with workflow creation/editing privileges can set this field to a javascript: URI; when a victim with access to the workflow clicks the associated link, the payload executes in the victim's browser session under n8n's origin. This is a classic stored XSS via insufficient URL scheme allowlisting, requiring some level of pre-existing collaborator/editor access to the n8n instance, and its impact is confined to the browser UI context rather than the agent/tool execution layer. Since n8n is increasingly used to orchestrate AI agent and tool-calling workflows, a compromised operator session from this XSS could subsequently be leveraged to tamper with agent configurations or credentials stored in the UI, but that is a secondary risk not detailed in this record.

Affected Systems

n8n

Detection Signatures

  • cachedResultUrl field containing javascript: scheme
  • Workflow JSON exports with non-http(s) URI schemes in resourceLocator fields
  • Unexpected window.open() calls triggered from workflow node UI elements
  • Audit logs showing workflow edits from low-privilege/editor accounts introducing scheme-anomalous URLs

Remediation Steps

  1. 1

    Upgrade n8n

    Update to n8n 1.123.64, 2.29.8, 2.30.1, or later, which validate/sanitize URI schemes before passing cachedResultUrl to window.open().

  2. 2

    Consult primary advisory

    Reference GHSA-9wcp-9r3j-383q for the authoritative, non-duplicate details, patches, and any updated severity/CVSS scoring.

  3. 3

    Restrict workflow edit permissions

    Limit workflow creation/editing privileges to trusted users until patched, since exploitation requires editor-level access.

  4. 4

    Input validation on stored URLs

    Enforce an allowlist of http/https schemes for any user- or workflow-controlled URL fields rendered or opened in the UI.

CVE / Advisory IDs

GHSA-h5xr-fqvj-253pGHSA-9wcp-9r3j-383q

Industries Most Exposed

Software/DevOps automationIT servicesany organization using n8n for workflow or AI-agent orchestration

Sources

Respond to this threat

Pro subscribers get a full AI-generated incident-response playbook for this threat — detection, containment, eradication, and recovery steps — plus an unlimited AI Threat Advisor for questions about your environment.