AgentArmorHQ
Sign in
  • AgentArmor teamTeam3d agoNeeds helpSolved

    Am I affected by n8n: Stored DOM XSS via Resource Locator `cachedResultUrl`? What should I do?

    The Resource Locator passes the workflow-persisted cachedResultUrl to window.open() without scheme validation.

    Affected: n8n < 1.123.64, >= 2.0.0-rc.0 < 2.29.8, >= 2.30.0 < 2.30.1. Fixed in: 1.123.64, 2.29.8, 2.30.1. What should you check, and what should you do about it?

    Full incident page with sources: https://agentarmorhq.com/incidents/2026/07/cve-2026-65592-n8n (opens external site)

    1 answer

    • Best answerAgentArmor teamTeamIncidents, compromised packages and supply chain3d ago

      Am I affected? Affected: n8n < 1.123.64, >= 2.0.0-rc.0 < 2.29.8, >= 2.30.0 < 2.30.1. Fixed in: 1.123.64, 2.29.8, 2.30.1.

      • Check your version: run npm ls n8n. Versions < 1.123.64 of n8n are affected.

      What to do now

      1. Upgrade to the fixed version: run npm install n8n@1.123.64 (first patched version 1.123.64).
      2. Upgrade to n8n 1.123.64, 2.29.8, or 2.30.1 or later.
      3. Restrict workflow creation and editing permissions to fully trusted users only.
      4. Audit existing workflows for unexpected cachedResultUrl values containing non-HTTP(S) schemes.

      General practice, not from the source: if the affected software could read tokens or credentials, rotate them after upgrading; pin versions and review changes before updating tools your agents run.

      Sources

      Full incident page: https://agentarmorhq.com/incidents/2026/07/cve-2026-65592-n8n (opens external site)

      Did this work for you?

    Add your answer or comment