Am I affected by n8n Git node lets a saved branch remote setting skip the sandbox path check and read…? What should I do?

Question

The Git node checked the repository that a fetch or pull targeted, but it wrote a `branch.<name>.remote` value into the repository's own configuration without checking that value.

Affected: n8n before 1.123.76, 2.0.0 to 2.37.7, and 2.38.0 to 2.38.2. Fixed in: 1.123.76, 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-86995-n8n

AgentArmor team · Accepted Answer

**Am I affected?**
Affected: n8n before 1.123.76, 2.0.0 to 2.37.7, and 2.38.0 to 2.38.2. Fixed in: 1.123.76, 2.37.7, and 2.38.2.
- Check your version: run `npm ls n8n`. Versions < 1.123.76 of n8n are affected.

**What to do now**
1. Upgrade to the fixed version: run `npm install n8n@1.123.76` (first patched version 1.123.76).
2. Upgrade to n8n 1.123.76, 2.37.7, or 2.38.2, or a later version.
3. If upgrading is not possible right away, restrict access to the n8n instance to fully trusted users only.
4. Disable the Git node by adding `n8n-nodes-base.git` to the `NODES_EXCLUDE` environment variable.
5. Run the n8n process under a dedicated low-privilege OS user account to limit the scope of filesystem access.

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**
- GitHub Advisory Database: https://github.com/advisories/GHSA-qgpw-8g46-w95v

Full incident page: https://agentarmorhq.com/incidents/2026/09/cve-2026-86995-n8n

Am I affected by n8n Git node lets a saved branch remote setting skip the sandbox path check and read…? What should I do?

1 answer

Add your answer or comment