n8n
Affected
- introduced
0, fixed1.123.76(semver)
Fixed versions
1.123.76
Fix
- Fixed version
1.123.76npm install [email protected]
Advisory
Also known as: CVE-2026-86995
n8n: Git Node branch.<name>.remote Config Key Bypasses Sandbox Path Restriction, Enabling Local Git Repository Read
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:
n8n-nodes-base.git to the NODES_EXCLUDE environment variable.These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
Medium Basis: The source's own band: MODERATE
0, fixed 1.123.76 (semver)1.123.76
1.123.76npm install [email protected]2.38.0, fixed 2.38.2 (semver)2.38.2
2.38.2npm install [email protected]2.0.0, fixed 2.37.7 (semver)2.37.7
2.37.7npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0