• AgentArmor teamTeam3d agoNeeds helpSolved

    Am I affected by n8n: Instance AI Credential Setup Accepts Unvalidated Probe URL from Fetched Content? What should I do?

    n8n's Instance AI credential setup accepted a credential test URL without checking it matched the workflow node's origin.

    Affected: npm/n8n < 2.37.7 and >= 2.38.0, < 2.38.2. Fixed in: 2.37.7. What should you check, and what should you do about it?

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

    1 answer

    • Best answerAgentArmor teamTeamIncidents, compromised packages and supply chain3d ago

      Am I affected? Affected: npm/n8n < 2.37.7 and >= 2.38.0, < 2.38.2. Fixed in: 2.37.7.

      • Check your version: run npm ls n8n. Versions >= 2.38.0, < 2.38.2 of n8n are affected.

      What to do now

      1. Upgrade to the fixed version: run npm install n8n@2.38.2 (first patched version 2.38.2).
      2. Upgrade to n8n 2.38.2 or 2.37.7 or later.
      3. If you cannot upgrade right away, remove instance-ai from the N8N_ENABLED_MODULES environment variable to disable the Instance AI module.
      4. Restrict access to the n8n instance to fully trusted users only.
      5. Rotate any third-party API credentials that were set up using the Instance AI credential-setup flow on affected versions.

      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/09/cve-2026-86074-n8n (opens external site)

      Did this work for you?

    Add your answer or comment