goauthentik.io
Affected
- introduced
0, fixed0.0.0-20251119140106-9dbdfc3f1be0(semver)
Fixed versions
0.0.0-20251119140106-9dbdfc3f1be0
Fix
- Fixed version
0.0.0-20251119140106-9dbdfc3f1be0go get [email protected]
Advisory
Also known as: BIT-authentik-2025-64521, CVE-2025-64521, GO-2025-4137, PYSEC-2025-237
authentik allows a deactivated Service account to authenticate to OAuth
Summary
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.
Patches
authentik 2025.8.5 and 2025.10.2 fix this issue, for other versions the workaround below can be used.
Workarounds
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
For more information
If you have any questions or comments about this advisory:
Medium Basis: The source's own band: MODERATE
0, fixed 0.0.0-20251119140106-9dbdfc3f1be0 (semver)0.0.0-20251119140106-9dbdfc3f1be0
0.0.0-20251119140106-9dbdfc3f1be0go get [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0