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

> Attackers can execute arbitrary commands on the server by manipulating Git node configurations in n8n workflow automation tools.

- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Sep 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-8jv2-7jr5-2p67, GHSA-mwp5-2m32-r54h, MINI-x3fq-2784-5vmq

## What is CVE-2026-85168?

CVE-2026-85168 is a high-severity command injection vulnerability in N8n N8n, published on 3 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2026-85168?

It affects 1 product.


Products: N8n N8n.

## How do I fix CVE-2026-85168?

Upgrade to a fixed version.

## Is CVE-2026-85168 being exploited?

There is no known exploitation of CVE-2026-85168 in the wild and no public exploit code.

Public exploit code:

- CVE-2026-85168 — n8n Git node RCE from repo-local filter.*.clean / merge-driver config on add|commit|checkout. Verified v2.35.3 / v2.36.2. (github_poc): https://github.com/Boreas37/CVE-2026-85168-PoC

## Other vulnerabilities in N8n N8n

- [CVE-2025-68613](https://insights.sbomify.com/CVE-2025-68613/): n8n Improper Control of Dynamically-Managed Code Resources (critical 10.0, exploited in the wild)
- [CVE-2026-21877](https://insights.sbomify.com/CVE-2026-21877/): n8n is vulnerable to Remote Code Execution via Arbitrary File Write (critical 10.0)
- [CVE-2026-21858](https://insights.sbomify.com/CVE-2026-21858/): n8n Vulnerable to Unauthenticated File Access via Improper Webhook Request Handling (critical 10.0)
- [CVE-2026-1470](https://insights.sbomify.com/CVE-2026-1470/): n8n Unsafe Workflow Expression Evaluation Allows Remote Code Execution (critical 9.9)
- [CVE-2025-68668](https://insights.sbomify.com/CVE-2025-68668/): n8n Vulnerable to Arbitrary Command Execution in Pyodide based Python Code Node (critical 9.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-85168 and fix it if it is affected.

What it is: CVE-2026-85168 is a high-severity command injection vulnerability in N8n N8n, published on 3 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-85168 in the wild and no public exploit code.

Affected product: N8n N8n. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-85168/ (Markdown: https://insights.sbomify.com/CVE-2026-85168/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-85168
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-85168
- OSV: https://osv.dev/vulnerability/CVE-2026-85168

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-85168/
Summaries are generated and may contain mistakes; the official description above is the record.