CVE-2026-72767
highPriorität · verfolgen · 35EPSS 0.009 · 59. PerzentilDEEUUSEPSS · bewertet 2026-10-27
n8n before 1.123.67, 2.x before 2.31.5, and 2.32.x before 2.32.1 contain a remote code execution vulnerability in the Git node. Authenticated users with rights to create and execute workflows can stage a crafted local repository that causes git to run hooks under default git security settings, executing arbitrary commands as the n8n process user. Both self-hosted and cloud instances are affected.
cvss
Technischer Schweregrad, 0–10. Eine Zeile je Quelle.
Basiswert 0–10 · höher = schwerwiegender · Vektor überfahren zum Auflösen⚠ Quellen uneinig · medium–high · 6.3–8.8
SSVC
Eine Handlungsentscheidung — aus Ausnutzung und Auswirkung.
schwächen
Die CWE-Schwächeklassen, zu denen dies gehört.
betroffene Produkte (15)
Betroffene Produkte und Versionsbereiche.
Advisories (2)
Hersteller- und Ökosystem-Meldungen dazu.
- WID-SEC-W-2026-2489n8n: Mehrere SchwachstellenDeutsch2026-07-22csaf · cert_bundDE
Ein Angreifer kann mehrere Schwachstellen in n8n ausnutzen, um Sicherheitsvorkehrungen zu umgehen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, um Dateien zu manipulieren, um einen SQL-Injection Angriff durchzuführen, und um beliebigen Programmcode auszuführen.
- GHSA-rcv6-pvrj-4xcgn8n: Authenticated code execution in the n8n Git node2026-07-22ghsa · osvUS
## Impact Authenticated n8n users with rights to create and execute workflows could achieve code execution on the n8n host. Using the Git node, under the default `git` security settings, by staging a crafted local repository, an attacker could cause `git` to run hooks, executing arbitrary commands as the n8n process user. Both self-hosted and cloud instances are affected where authenticated users can create and execute workflows using the Git node. ## Patches The issue has been fixed in n8n versions 1.123.67, 2.31.5, and 2.32.1. 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. - Restrict network egress from the n8n instance to limit the impact of arbitrary code execution. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
auch bekannt als (3)
Weitere Namen und Kennungen dieser Entität.
quellen
Welche Quellen diesen Datensatz belegen und wann.
Referenzen (6)
Externe Belege — Patches, Meldungen, Analysen.
- https://github.com/n8n-io/n8n/security/advisories/GHSA-rcv6-pvrj-4xcgcnnvd
- https://www.vulncheck.com/advisories/n8n-before-remote-code-execution-via-git-nodecnnvd
- https://github.com/n8n-io/n8n/security/advisories/GHSA-rcv6-pvrj-4xcgenisa_euvd
- https://www.vulncheck.com/advisories/n8n-before-remote-code-execution-via-git-nodeenisa_euvd
- https://github.com/n8n-io/n8n/security/advisories/GHSA-rcv6-pvrj-4xcgMitigationVendor Advisorynvd
- https://www.vulncheck.com/advisories/n8n-before-remote-code-execution-via-git-nodeThird Party Advisorynvd
Angreifer nutzen Schwachstellen wie diese gegen im Internet exponierte Dienste aus. Sehen Sie mit einem kostenlosen Passiv-Scan, was exponiert ist.
Kostenloser Scan