Quick answers
- Is CVE-2026-40166 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-40166 being exploited in the wild.
- How severe is CVE-2026-40166?
- Informational severity, with a CVSS score of 7.1, published 22 May 2026.
- Which products and versions are affected?
- Goauthentik Authentik < 2025.12.5, >= 2026.2.0-rc1, < 2026.2.3.
- Is there a fix for CVE-2026-40166?
- A patch was published on 2026-05-12: Versions 2025.12.5 and 2026.2.3 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-40166 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-40166?
- Check whether you run Goauthentik Authentik at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An information disclosure vulnerability exists in the authentik API endpoint 'GET /api/v3/oauth2/access_tokens/'. The root cause is an authorization failure where the API response includes a nested provider object containing the 'client_id' and 'client_secret' for confidential OAuth2 providers. To exploit this, an attacker must be an authenticated non-admin user who has previously completed an OAuth2 flow against a confidential provider. Successful exploitation allows the attacker to retrieve the provider's secret, which could be used to facilitate unauthorized credential reuse. The issue is fixed in versions 2025.12.5 and 2026.2.3.
Affected products
- goauthentik authentik < 2025.12.5, >= 2026.2.0-rc1, < 2026.2.3
Timeline
- 2026-05-12: patched: Versions 2025.12.5 and 2026.2.3 released
- 2026-05-12: advisory: GitHub Security Advisory GHSA-hhpc-rqgm-pxj4 published
- 2026-05-22: disclosed: CVE-2026-40166 published to NVD