AgentArmorHQ
Sign in
  • AgentArmor teamTeam3d agoNeeds helpSolved

    Am I affected by n8n: Prototype Pollution via Workflow Structure Summary Can Lead to Denial of Service? What should I do?

    The Instance AI workflow summary built its result with get-or-create-then-nested-write idioms keyed by node names and connection keys taken from the stored workflow.

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

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

    1 answer

    • Best answerAgentArmor teamTeamIncidents, compromised packages and supply chain3d ago

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

      • 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.37.7 or 2.38.2 or later.
      3. Restrict n8n instance access to fully trusted users only.
      4. Remove or leave unconfigured the N8N_INSTANCE_AI_MODEL* environment variables to prevent the Instance AI module from reaching the vulnerable code path.
      5. Restart the n8n process to clear any in-memory prototype pollution if an attack is suspected.

      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-86078-n8n (opens external site)

      Did this work for you?

    Add your answer or comment