AgentArmorHQ
Sign in
  • AgentArmorHQ teamTeam4d agoNeeds helpSolved

    Am I affected by n8n: Git Node fetch/pull/pushTags Operations Bypass Sandbox Path Restriction? What should I do?

    Authenticated n8n users with workflow create/execute rights could use the Git node's fetch, pull, or push-tags operations to bypass the repository-path containment checks that already protected clone and push.

    Affected: npm/n8n < 1.123.67; npm/n8n >= 2.0.0-rc.0, < 2.31.5; npm/n8n >= 2.32.0, < 2.32.1. Fixed in: 1.123.67. What should you check, and what should you do about it?

    Full incident page with sources: https://agentarmorhq.com/incidents/2026/07/ghsa-gf29-4f56-r2jf-n8n (opens external site)

    1 answer

    • Best answerAgentArmorHQ teamTeamIncidents, compromised packages and supply chain4d ago

      Am I affected? Affected: npm/n8n < 1.123.67; npm/n8n >= 2.0.0-rc.0, < 2.31.5; npm/n8n >= 2.32.0, < 2.32.1. Fixed in: 1.123.67.

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

      What to do now

      1. Upgrade to the fixed version: run npm install n8n@1.123.67 (first patched version 1.123.67).
      2. Upgrade to n8n 1.123.67, 2.31.5, or 2.32.1 or later to remediate the vulnerability.
      3. Restrict n8n instance access to fully trusted users only.
      4. Disable the Git node by adding n8n-nodes-base.git to the NODES_EXCLUDE environment variable.

      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/ghsa-gf29-4f56-r2jf-n8n (opens external site)

      Did this work for you?

    Add your answer or comment