{"id":"EUVD-2026-74272","enisaUuid":"5ae590a6-c0fe-32b5-8254-3009be1f7d58","description":"n8n is an open source workflow automation platform. Prior to 1.123.76, 2.37.7, and 2.38.2, the public OIDC login and callback endpoints completed authentication even when OIDC was not the enabled active authentication method. An Enterprise administrator who had configured and later disabled an identity provider still exposed a working route that could issue valid sessions. The affected logic is packages/cli/src/modules/sso-oidc/oidc.service.ee.ts, including generateLoginUrl and the callback flow that lacked assertOidcLoginEnabled. This issue is fixed in versions 1.123.76, 2.37.7 and 2.38.2.","datePublished":"Sep 8, 2026, 9:21:55 PM","dateUpdated":"Sep 9, 2026, 1:50:25 PM","baseScore":6.0,"baseScoreVersion":"4.0","baseScoreVector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N","references":"https://github.com/n8n-io/n8n/security/advisories/GHSA-pf83-w3f9-8m37\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-86084\nGHSA-pf83-w3f9-8m37\n","assigner":"GitHub_M","epss":0.46,"enisaIdProduct":[{"id":"3bcba757-55ef-30c3-970f-dda8f78b0213","product":{"name":"n8n","vendor":{"name":"n8n-io"}},"product_version":"2.38.0, \u003c 2.38.2"},{"id":"4eca4d10-7dea-3a6b-b9bd-e9e799c8044a","product":{"name":"n8n","vendor":{"name":"n8n-io"}},"product_version":"\u003c 1.123.76"},{"id":"5ff14b5e-fd68-3731-a775-dca0ee139874","product":{"name":"n8n","vendor":{"name":"n8n-io"}},"product_version":"2.0.0, \u003c 2.37.7"}],"enisaIdVendor":[{"id":"865d4f61-9776-3cfb-8de1-2185d8320525","vendor":{"name":"n8n-io"}}],"enisaIdVulnerability":[{"id":"e510285c-6367-3278-9434-a288c512b2f3","vulnerability":{"id":"GHSA-pf83-w3f9-8m37","description":"n8n: Disabled OIDC SSO Endpoints Remain Active and Issue Valid Sessions","datePublished":"Sep 10, 2026, 9:07:24 PM","dateUpdated":"Sep 10, 2026, 9:07:24 PM","baseScore":0.0,"references":"https://github.com/n8n-io/n8n/security/advisories/GHSA-pf83-w3f9-8m37\nhttps://nvd.nist.gov/vuln/detail/CVE-2026-86084\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-74272\n","aliases":"GHSA-pf83-w3f9-8m37\nCVE-2026-86084\n","epss":0.0,"dataProcessed":"Nov 15, 2026, 2:54:50 AM","vulnerabilityProduct":[],"vulnerabilityVendor":[]}},{"id":"f372206f-b0dc-39b7-b112-6207cc4c3540","vulnerability":{"id":"CVE-2026-86084","description":"n8n is an open source workflow automation platform. Prior to 1.123.76, 2.37.7, and 2.38.2, the public OIDC login and callback endpoints completed authentication even when OIDC was not the enabled active authentication method. An Enterprise administrator who had configured and later disabled an identity provider still exposed a working route that could issue valid sessions. The affected logic is packages/cli/src/modules/sso-oidc/oidc.service.ee.ts, including generateLoginUrl and the callback flow that lacked assertOidcLoginEnabled. This issue is fixed in versions 1.123.76, 2.37.7 and 2.38.2.","datePublished":"Sep 8, 2026, 9:21:55 PM","dateUpdated":"Sep 9, 2026, 1:50:25 PM","status":"PUBLISHED","baseScore":6.0,"baseScoreVersion":"4.0","baseScoreVector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N","references":"https://github.com/n8n-io/n8n/security/advisories/GHSA-pf83-w3f9-8m37\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-74272\n","assigner":"GitHub_M","epss":0.46,"dataProcessed":"Nov 15, 2026, 7:17:41 AM","vulnerabilityProduct":[{"id":"00d8cf73-c758-3759-83e7-266a623872da","product":{"name":"n8n","vendor":{"name":"n8n-io"}},"product_version":"\u003c 1.123.76"},{"id":"215bfb32-b71b-3b2c-adc8-4df65be47232","product":{"name":"n8n","vendor":{"name":"n8n-io"}},"product_version":"2.38.0, \u003c 2.38.2"},{"id":"6c2c5b8e-5a45-3f88-adea-661b224cf0b2","product":{"name":"n8n","vendor":{"name":"n8n-io"}},"product_version":"2.0.0, \u003c 2.37.7"}],"vulnerabilityVendor":[{"id":"9ee378f0-d339-320b-aa1b-9b2bfc480a07","vendor":{"name":"n8n-io"}}]}}],"enisaIdAdvisory":[{"id":"be56b96f-5341-3208-b60d-ee3e007d13a4","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"}}}]}}]}