The vulnerability in n8n's Git node arises because it validates a relative remote URL against a configured repository path but then invokes git with that path as the working directory. Git resolves the URL relative to the enclosing repository's top level, which can be outside the sandbox. An authenticated user can exploit this by nesting a repository one level below the configured path, causing the URL to pass the file-access check while git accesses repositories outside the sandbox. This allows reading git repository objects outside the restricted path. The fix in n8n versions 1.123.76, 2.37.7, and 2.38.2 ensures the remote reference is resolved from the actual git working directory before applying sandbox restrictions. Disabling the Git node is a recommended workaround.

An authenticated user with member privileges can bypass file access restrictions in the Git node to read git repository contents outside the configured sandbox path. This could expose sensitive repository data not intended to be accessible within the n8n environment. The vulnerability does not allow privilege escalation or remote code execution but compromises data confidentiality within the affected git repositories.

The vulnerability is fixed in n8n versions 1.123.76, 2.37.7, and 2.38.2. Users should upgrade to these versions or later to remediate the issue. As a workaround, the Git node can be disabled by adding 'n8n-nodes-base.git' to the NODES_EXCLUDE configuration setting. No other actions are specifically required.