| Package | Affected versions | Patched versions |
|---|---|---|
| goauthentik.io | < 0.0.0-20251119140106-9dbdfc3f1be0all versions | 0.0.0-20251119140106-9dbdfc3f1be0 |
| authentik-client | ≥ 2025.10.0, < 2025.10.2≥ 2025.8.0, < 2025.8.5 | 2025.10.22025.8.5 |
| authentik | ≥ 2025.10.0, < 2025.10.2≥ 2025.8.0, < 2025.8.5 | 2025.10.22025.8.5 |
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 2025.8.5 and 2025.10.2 fix this issue, for other versions the workaround below can be used.
You can add a policy to your application that explicitly checks if the service account is still valid, and deny access if not.
return request.user.is_active
If you have any questions or comments about this advisory:
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free