n8n: path traversal
MediumCVE-2026-86995 · Published Sep 10, 2026
## Impact The Git node validated the repository that a fetch or pull targeted, but `setUpstream` wrote a `branch.<name>.remote` value into the repository's own configuration without validating it. A subsequent fetch or pull resolved the remote from that configuration rather than from the checked parameter, so an authenticated user with workflow-edit permission could point it at any local repository the n8n process could read and receive its contents. The patch validates the branch remote configuration on the same terms as the repository parameter. ## Patches The issue has been fixed in n8n versions 1.123.76, 2.37.7, and 2.38.2. Users should upgrade to one of these versions or later to remediate the vulnerability. ## Workarounds If upgrading is not immediately possible, administrators should consider the following temporary mitigations: - Restrict n8n instance access to fully trusted users only. - Disable the Git node by adding `n8n-nodes-base.git` to the `NODES_EXCLUDE` environment variable. - Ensure the n8n process runs under a dedicated low-privilege OS user account to limit the scope of any filesystem access. These workarounds do not fully remediate the risk and should onl...
Affected versions
| Package | Affected | Fixed in |
|---|---|---|
| n8n npm | < 1.123.76 | 1.123.76 |
| >= 2.38.0, < 2.38.2 | 2.38.2 | |
| >= 2.0.0, < 2.37.7 | 2.37.7 |
Details and references
## Impact The Git node validated the repository that a fetch or pull targeted, but `setUpstream` wrote a `branch.<name>.remote` value into the repository's own configuration without validating it. A subsequent fetch or pull resolved the remote from that configuration rather than from the checked parameter, so an authenticated user with workflow-edit permission could point it at any local repository the n8n process could read and receive its contents. The patch validates the branch remote configuration on the same terms as the repository parameter. ## Patches The issue has been fixed in n8n versions 1.123.76, 2.37.7, and 2.38.2. Users should upgrade to one of these versions or later to remediate the vulnerability. ## Workarounds If upgrading is not immediately possible, administrators should consider the following temporary mitigations: - Restrict n8n instance access to fully trusted users only. - Disable the Git node by adding `n8n-nodes-base.git` to the `NODES_EXCLUDE` environment variable. - Ensure the n8n process runs under a dedicated low-privilege OS user account to limit the scope of any filesystem access. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
More n8n advisories
All n8n| Date | Advisory | Severity | Fixed in |
|---|---|---|---|
| Sep 10 | n8n: Per-Resource OAuth Consent Bypass via Unbound Refresh Token Resource Substitution MediumSep 10 | Medium | 2.37.7+1 more |
| Sep 10 | n8n: Instance AI Credential Setup Accepts Unvalidated Probe URL from Fetched ContentMediumSep 10 | Medium | 2.37.7+1 more |
| Sep 10 | n8n: missing authorizationMediumSep 10 | Medium | 2.37.7+1 more |
| Sep 10 | n8n: Log Streaming Event Destinations Decrypt Generic-Auth Credentials Without Ownership CheckMediumSep 10 | Medium | 1.123.76+2 more |
| Sep 10 | n8n: Disabled OIDC SSO Endpoints Remain Active and Issue Valid SessionsMediumSep 10 | Medium | 1.123.76+2 more |
| Sep 10 | n8n: GitHub Trigger 422 Reuse Path Skips Webhook Secret Storage, Causing Signature Verification to Fail-OpenMediumSep 10 | Medium | 1.123.76+2 more |