CVE-2026-85168: n8n before 1.123.73 Remote Code Execution via Git Node

Published Sep 3, 2026
·
Updated

n8n versions before 1.123.73, 2.35.4, and 2.36.2 contain a remote code execution vulnerability in the Git node. The node reset a fixed list of command-bearing configuration keys before each operation, but that list did not cover the content-filter and merge-driver key families. A repository with local configuration setting one of those keys together with a matching attribute pattern causes git to execute the configured command during an ordinary Add, Commit, Checkout, or Pull operation. The command runs as the n8n process user.

Affected Software

1 affected component
n8n n8n<1.123.73, =2.35.4, =2.36.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade n8n Git node to a version that resolves this vulnerability.

    Fixed in 1.123.73
  2. Upgrade

    Upgrade n8n Git node to a version that resolves this vulnerability.

    Fixed in 2.35.4
  3. Upgrade

    Upgrade n8n Git node to a version that resolves this vulnerability.

    Fixed in 2.36.2

Event History

Sep 3, 2026
CVE Published
via MITRE·11:22 AM
Data Sourced
via MITRE·11:22 AM
DescriptionWeakness

Frequently Asked Questions

1

Who is exposed to exploitation?

n8n instances that use the Git node with a repository whose local Git configuration can be supplied or modified by an attacker are exposed. Exploitation occurs when the Git node performs an Add, Commit, Checkout, or Pull operation against that repository.

2

What must an attacker control to trigger code execution?

The attacker needs to place a command-bearing content-filter or merge-driver configuration key in the repository's local Git configuration and provide a matching attribute pattern. The configured command is then invoked during a relevant ordinary Git operation.

3

What privileges does the executed command receive?

The command runs as the n8n process user. Its access is therefore limited or expanded according to the permissions assigned to that n8n service account.

4

Which versions are affected and what should be upgraded?

Versions before 1.123.73, 2.35.4, and 2.36.2 are affected. Upgrade to the applicable fixed version for the version line you are using.

5

What can be done if upgrading is not immediately possible?

Avoid using the Git node to perform Add, Commit, Checkout, or Pull operations on repositories that are untrusted or can be modified by untrusted parties. Review repository-local Git configuration and attributes for content-filter or merge-driver settings before allowing the node to operate on a repository.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203