CVE-2026-86084: n8n: Disabled OIDC SSO Endpoints Remain Active and Issue Valid Sessions
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
n8nto a version that resolves this vulnerability.Fixed in 1.123.76 - Upgrade
Upgrade
n8nto a version that resolves this vulnerability.Fixed in 2.37.7 - Upgrade
Upgrade
n8nto a version that resolves this vulnerability.Fixed in 2.38.2
Event History
Frequently Asked Questions
Which deployments are exposed?
Deployments running versions before 1.123.76, 2.37.7, or 2.38.2 are affected if an Enterprise administrator configured an OIDC identity provider and later disabled it. The public OIDC login and callback routes could remain usable despite OIDC no longer being the active authentication method.
What does an attacker need to exploit this issue?
An attacker needs to use the public OIDC login and callback flow associated with an identity provider that was previously configured. The vulnerable flow could complete authentication and issue a valid session even though OIDC had been disabled.
How can I remediate the issue?
Upgrade n8n to version 1.123.76, 2.37.7, or 2.38.2. These releases add the missing enabled-state enforcement for the OIDC login URL generation and callback flow.