{"id":"EUVD-2026-74268","enisaUuid":"e6ca2507-a284-36b6-94f7-56ce700c60cb","description":"n8n is an open source workflow automation platform. Prior to 1.123.76, 2.37.7, and 2.38.2, the Git node validated the repository parameter for fetch or pull, but setUpstream wrote a branch..remote value into repository configuration without validating it. A later fetch or pull resolved the remote from that configuration instead of the checked parameter. An authenticated workflow editor could therefore point Git at any local repository readable by the n8n process and receive its contents through packages/nodes-base/nodes/Git/GenericFunctions.ts. This issue is fixed in versions 1.123.76, 2.37.7 and 2.38.2.","datePublished":"Sep 8, 2026, 9:17:38 PM","dateUpdated":"Sep 9, 2026, 1:34:48 PM","baseScore":5.3,"baseScoreVersion":"4.0","baseScoreVector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N","references":"https://github.com/n8n-io/n8n/security/advisories/GHSA-qgpw-8g46-w95v\nhttps://github.com/n8n-io/n8n/releases/tag/n8n@1.123.76\nhttps://github.com/n8n-io/n8n/releases/tag/n8n@2.37.7\nhttps://github.com/n8n-io/n8n/releases/tag/n8n@2.38.2\n","aliases":"CVE-2026-86995\nGHSA-qgpw-8g46-w95v\n","assigner":"GitHub_M","epss":0.41,"enisaIdProduct":[{"id":"7b4d372b-45ce-3b94-9771-96d9ab80eec7","product":{"name":"n8n","vendor":{"name":"n8n-io"}},"product_version":"\u003c 1.123.76"},{"id":"c188bfae-57ac-397b-9bc4-99a0ddc546f2","product":{"name":"n8n","vendor":{"name":"n8n-io"}},"product_version":"2.0.0, \u003c 2.37.7"},{"id":"f481abf5-a7a9-38a1-82ff-39211cdff5c8","product":{"name":"n8n","vendor":{"name":"n8n-io"}},"product_version":"2.38.0, \u003c 2.38.2"}],"enisaIdVendor":[{"id":"ab91a0dd-41a7-3118-9b0e-c04a13ffb5e3","vendor":{"name":"n8n-io"}}],"enisaIdVulnerability":[{"id":"57e9a0d4-fe11-3cdc-b0ce-03758dbb5541","vulnerability":{"id":"GHSA-qgpw-8g46-w95v","description":"n8n: Git Node branch.\u003cname\u003e.remote Config Key Bypasses Sandbox Path Restriction, Enabling Local Git Repository Read","datePublished":"Sep 10, 2026, 9:16:36 PM","dateUpdated":"Sep 10, 2026, 9:16:36 PM","baseScore":0.0,"references":"https://github.com/n8n-io/n8n/security/advisories/GHSA-qgpw-8g46-w95v\nhttps://nvd.nist.gov/vuln/detail/CVE-2026-86995\nhttps://github.com/n8n-io/n8n\nhttps://github.com/n8n-io/n8n/releases/tag/n8n@1.123.76\nhttps://github.com/n8n-io/n8n/releases/tag/n8n@2.37.7\nhttps://github.com/n8n-io/n8n/releases/tag/n8n@2.38.2\n","enisa_id":"EUVD-2026-74268\n","aliases":"CVE-2026-86995\nGHSA-qgpw-8g46-w95v\n","epss":0.0,"dataProcessed":"Nov 15, 2026, 2:54:50 AM","vulnerabilityProduct":[],"vulnerabilityVendor":[]}},{"id":"b0252573-b8ec-3ad0-b2c4-6600e69d65e4","vulnerability":{"id":"CVE-2026-86995","description":"n8n is an open source workflow automation platform. Prior to 1.123.76, 2.37.7, and 2.38.2, the Git node validated the repository parameter for fetch or pull, but setUpstream wrote a branch..remote value into repository configuration without validating it. A later fetch or pull resolved the remote from that configuration instead of the checked parameter. An authenticated workflow editor could therefore point Git at any local repository readable by the n8n process and receive its contents through packages/nodes-base/nodes/Git/GenericFunctions.ts. This issue is fixed in versions 1.123.76, 2.37.7 and 2.38.2.","datePublished":"Sep 8, 2026, 9:17:38 PM","dateUpdated":"Sep 9, 2026, 1:34:48 PM","status":"PUBLISHED","baseScore":5.3,"baseScoreVersion":"4.0","baseScoreVector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N","references":"https://github.com/n8n-io/n8n/security/advisories/GHSA-qgpw-8g46-w95v\nhttps://github.com/n8n-io/n8n/releases/tag/n8n@1.123.76\nhttps://github.com/n8n-io/n8n/releases/tag/n8n@2.37.7\nhttps://github.com/n8n-io/n8n/releases/tag/n8n@2.38.2\n","enisa_id":"EUVD-2026-74268\n","assigner":"GitHub_M","epss":0.41,"dataProcessed":"Nov 15, 2026, 7:17:47 AM","vulnerabilityProduct":[{"id":"21db9e67-f7d9-36e2-8835-a821919ea3ff","product":{"name":"n8n","vendor":{"name":"n8n-io"}},"product_version":"2.0.0, \u003c 2.37.7"},{"id":"701df1b0-d043-3c83-adfd-c370e731dc2b","product":{"name":"n8n","vendor":{"name":"n8n-io"}},"product_version":"\u003c 1.123.76"},{"id":"e59e0f87-9021-345b-a4d1-fe691ab3702b","product":{"name":"n8n","vendor":{"name":"n8n-io"}},"product_version":"2.38.0, \u003c 2.38.2"}],"vulnerabilityVendor":[{"id":"d52c46d8-530a-36f5-9a79-5da61cf4d131","vendor":{"name":"n8n-io"}}]}}],"enisaIdAdvisory":[{"id":"8ee88508-c1d2-317f-af43-73ec53b4de4a","advisory":{"id":"WID-SEC-W-2026-3165","description":"n8n: Mehrere Schwachstellen","summary":"Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in n8n ausnutzen, um Sicherheitsmechanismen zu umgehen, beliebigen Code auszuführen oder einen Denial of Service zu verursachen.","datePublished":"Sep 2, 2026, 10:00:00 PM","dateUpdated":"Sep 16, 2026, 10:00:00 PM","baseScore":0.0,"references":"https://wid.cert-bund.de/.well-known/csaf/white/2026/wid-sec-w-2026-3165.json\nhttps://wid.cert-bund.de/portal/wid/securityadvisory?name\u003dWID-SEC-2026-3165\n","aliases":"CVE-2026-86074\nCVE-2026-86075\nCVE-2026-86076\nCVE-2026-86077\nCVE-2026-86078\nCVE-2026-86079\nCVE-2026-86080\nCVE-2026-86081\nCVE-2026-86082\nCVE-2026-86083\nCVE-2026-86084\nCVE-2026-86085\nCVE-2026-86993\nCVE-2026-86994\nCVE-2026-86995\nCVE-2026-86996\nCVE-2026-92587\nCVE-2026-92588\n","source":{"id":8,"name":"csaf_certbund"},"advisoryProduct":[{"id":"052f3481-6e57-3161-854a-dd4ae6a2d69f","product":{"name":"n8n","vendor":{"name":"n8n-io"}}},{"id":"81619e09-3fd2-31b6-91fd-afad3c842089","product":{"name":"1.123.76","vendor":{"name":"n8n"}}},{"id":"d8889809-274c-3db0-9b0f-65ed9efedb6e","product":{"name":"2.37.7","vendor":{"name":"open source"}}},{"id":"ed4e7b5b-16db-3513-8d06-d79b44fc34f0","product":{"name":"2.38.2","vendor":{"name":"n8n"}}}]}}]}