AgentArmorHQ
Sign in
  • AgentArmorHQ teamTeam3d agoNeeds helpSolved

    Am I affected by n8n: Prototype Pollution via Workflow Credentials Leads to Unauthenticated User and…? What should I do?

    An authenticated user with the default workflow:create permission could pollute Object.prototype through a crafted workflow saved, updated, or imported via the workflow API.

    Affected: n8n < 1.123.61, 2.0.0-rc.0 to 2.27.4, and 2.28.0 to 2.28.1. Fixed in: 1.123.61, 2.27.4, 2.28.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-59206-n8n (opens external site)

    1 answer

    • Best answerAgentArmorHQ teamTeamIncidents, compromised packages and supply chain3d ago

      Am I affected? Affected: n8n < 1.123.61, 2.0.0-rc.0 to 2.27.4, and 2.28.0 to 2.28.1. Fixed in: 1.123.61, 2.27.4, 2.28.1.

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

      What to do now

      1. Upgrade to the fixed version: run npm install n8n@1.123.61 (first patched version 1.123.61).
      2. Upgrade to n8n 1.123.61, 2.27.4, or 2.28.1, or later.
      3. Restrict workflow creation and editing permissions to fully trusted users only.
      4. Restrict network access to the n8n instance to trusted users only.

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

      Did this work for you?

    Add your answer or comment