{"id":"EUVD-2026-74276","enisaUuid":"776ec1f3-c96a-33ce-bf1a-4520e7b44a19","description":"n8n is an open source workflow automation platform. Prior to 1.123.76, 2.37.7, and 2.38.2, the GitHub Trigger generated a webhook secret but discarded it when GitHub returned HTTP 422 and the node reused an existing webhook. Workflow static data then retained webhookId without webhookSecret, and X-Hub-Signature-256 verification accepted deliveries without a stored secret. The affected logic includes packages/nodes-base/nodes/Github/GithubTriggerHelpers.ts and the 422 webhook reuse path. This issue is fixed in versions 1.123.76, 2.37.7 and 2.38.2.","datePublished":"Sep 8, 2026, 9:25:48 PM","dateUpdated":"Sep 9, 2026, 1:16:31 PM","baseScore":6.3,"baseScoreVersion":"4.0","baseScoreVector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","references":"https://github.com/n8n-io/n8n/security/advisories/GHSA-5m98-cgcr-xx3q\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-86080\nGHSA-5m98-cgcr-xx3q\n","assigner":"GitHub_M","epss":0.26,"enisaIdProduct":[{"id":"437211b8-7dbc-3b32-91c2-f57e859a496f","product":{"name":"n8n","vendor":{"name":"n8n-io"}},"product_version":"\u003c 1.123.76"},{"id":"b6e84ae0-40dc-3c8b-b639-68623889f4f1","product":{"name":"n8n","vendor":{"name":"n8n-io"}},"product_version":"2.38.0, \u003c 2.38.2"},{"id":"b94b4cf8-cef8-3088-a1f1-157e422c0dbb","product":{"name":"n8n","vendor":{"name":"n8n-io"}},"product_version":"2.0.0, \u003c 2.37.7"}],"enisaIdVendor":[{"id":"838a5abb-8a9b-3070-8311-6f22f823e4b0","vendor":{"name":"n8n-io"}}],"enisaIdVulnerability":[{"id":"1359e38f-d984-30d9-b88e-753138658ade","vulnerability":{"id":"GHSA-5m98-cgcr-xx3q","description":"n8n: GitHub Trigger 422 Reuse Path Skips Webhook Secret Storage, Causing Signature Verification to Fail-Open","datePublished":"Sep 10, 2026, 9:06:37 PM","dateUpdated":"Sep 10, 2026, 9:06:37 PM","baseScore":0.0,"references":"https://github.com/n8n-io/n8n/security/advisories/GHSA-5m98-cgcr-xx3q\nhttps://nvd.nist.gov/vuln/detail/CVE-2026-86080\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-74276\n","aliases":"GHSA-5m98-cgcr-xx3q\nCVE-2026-86080\n","epss":0.0,"dataProcessed":"Nov 15, 2026, 2:54:50 AM","vulnerabilityProduct":[],"vulnerabilityVendor":[]}},{"id":"5698eb7b-cb2c-3f9a-83a3-c6a30968f702","vulnerability":{"id":"CVE-2026-86080","description":"n8n is an open source workflow automation platform. Prior to 1.123.76, 2.37.7, and 2.38.2, the GitHub Trigger generated a webhook secret but discarded it when GitHub returned HTTP 422 and the node reused an existing webhook. Workflow static data then retained webhookId without webhookSecret, and X-Hub-Signature-256 verification accepted deliveries without a stored secret. The affected logic includes packages/nodes-base/nodes/Github/GithubTriggerHelpers.ts and the 422 webhook reuse path. This issue is fixed in versions 1.123.76, 2.37.7 and 2.38.2.","datePublished":"Sep 8, 2026, 9:25:48 PM","dateUpdated":"Sep 9, 2026, 1:16:31 PM","status":"PUBLISHED","baseScore":6.3,"baseScoreVersion":"4.0","baseScoreVector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","references":"https://github.com/n8n-io/n8n/security/advisories/GHSA-5m98-cgcr-xx3q\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-74276\n","assigner":"GitHub_M","epss":0.26,"dataProcessed":"Nov 15, 2026, 7:17:41 AM","vulnerabilityProduct":[{"id":"2676657f-4890-3fd2-ad24-175939f745a2","product":{"name":"n8n","vendor":{"name":"n8n-io"}},"product_version":"2.38.0, \u003c 2.38.2"},{"id":"6b2cad77-eb66-349b-b2c0-f4b7fb15cb75","product":{"name":"n8n","vendor":{"name":"n8n-io"}},"product_version":"2.0.0, \u003c 2.37.7"},{"id":"93c6ff15-d8ef-3958-8465-9802f1131d50","product":{"name":"n8n","vendor":{"name":"n8n-io"}},"product_version":"\u003c 1.123.76"}],"vulnerabilityVendor":[{"id":"8cb0f392-a2df-375f-95c1-96a31b35e809","vendor":{"name":"n8n-io"}}]}}],"enisaIdAdvisory":[{"id":"32a4fb85-12e0-381b-b81a-ede81acad7f5","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"}}}]}}]}