INCIDENT MAP

Browse / AI Framework and Platform Flaws / CVE-2026-86084

n8n: Disabled OIDC SSO Endpoints Remain Active and Issue Valid Sessions

CVE-2026-86084 ยท 2026-09-10 moderate

Class
AI Framework and Platform Flaws (filed by a model that read the advisory)
Technique
Authentication and access control
Affected
n8n (npm)
Gets past
Authentication check
CVSS
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
EPSS
0.5% chance of exploitation in 30 days

How it works, in short

OIDC login and callback endpoints keep issuing sessions after the provider is disabled because they do not check whether OIDC is the active method. (Our summary, written by a model. The source text is below.)

Details

Impact

The public OIDC login and callback endpoints ran the full flow whether or not OIDC was the instance's active, enabled authentication method, so turning OIDC off in Settings did not stop it issuing sessions. An administrator who disabled the provider still had a working login route. The patch requires OIDC to be the enabled, active authentication method before either endpoint starts the flow or issues a session.

The issue affects n8n Enterprise instances where OIDC was configured at least once and subsequently disabled.

Patches

The issue has been fixed in n8n versions 1.123.76, 2.37.7, and 2.38.2. 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:
- Disable or revoke the corresponding application or client at the IdP level to prevent the OIDC flow from completing.
- Restrict network-level access to the n8n instance to trusted users only.

These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

References

Source: GitHub Advisory Database, used under CC BY 4.0.