GHSA-qgpw-8g46-w95v n8n: Git Node branch.<name>.remote Config Key Bypasses Sandbox Path Restriction, Enabling Local Git Repository Read

• npm n8n: < 1.123.76 → fixed in 1.123.76 • npm n8n: >= 2.38.0, < 2.38.2 → fixed in 2.38.2 • npm n8n: >= 2.0.0, < 2.37.7 → fixed in 2.37.7

Impact The Git node validated the repository that a fetch or pull targeted, but `setUpstream` wrote a `branch..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.