BIT-authentik-2025-64521
See a problem?- Import Source
- https://github.com/bitnami/vulndb/tree/main/data/authentik/BIT-authentik-2025-64521.json
- JSON Data
- https://api.osv.dev/v1/vulns/BIT-authentik-2025-64521
- Aliases
- Published
- 2026-04-16T23:36:29Z
- Modified
- 2026-09-08T08:45:39Z
- Summary
- authentik deactivated service accounts can authenticate to OAuth
- Details
-
authentik is an open-source Identity Provider. Prior to versions 2025.8.5 and 2025.10.2, when authenticating with client_id and client_secret to an OAuth provider, authentik creates a service account for the provider. In previous authentik versions, authentication for this account was possible even when the account was deactivated. Other permissions are correctly applied and federation with other providers still take assigned policies correctly into account. authentik versions 2025.8.5 and 2025.10.2 fix this issue. A workaround involves adding a policy to the application that explicitly checks if the service account is still valid, and deny access if not.
- Database specific
{ "cpes": [ "cpe:2.3:a:goauthentik:authentik:*:*:*:*:*:go:*:*" ], "severity": "Medium" }- References
Affected packages
Bitnami / authentik
Package
- Name
- authentik
- Purl
- pkg:bitnami/authentik
Severity
- 4.8 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N CVSS Calculator