Skip to content
OpenAdvisories
Medium · 4.8 CVE-2025-64521 BIT-authentik-2025-64521EUVD-2025-198186GHSA-xr73-jq5p-ch8rGO-2025-4137PYSEC-2025-237

authentik deactivated service accounts can authenticate to OAuth

Published Nov 19, 2025 · Updated Nov 19, 2025 · Assigned by GitHub_M

Description

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.

Affected products

VendorProductAffectedFixed
goauthentik authentik < 2025.10.2, < 2025.8.5 —

Fixed in Linux distributions

Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.

ReleasePackageFixed inAdvisory
openSUSE Leap 16.0 govulncheck-vulndb 0.0.20260723T184607-160000.1.1 openSUSE-SU-2026:21483-1
openSUSE Leap 15.6 govulncheck-vulndb 0.0.20251230T014957-150000.1.134.1 SUSE-SU-2026:0037-1

Affected packages

EcosystemPackageAffectedFixedRecord
Go goauthentik.io < 0.0.0-20251119140106-9dbdfc3f1be0 0.0.0-20251119140106-9dbdfc3f1be0 GHSA-xr73-jq5p-ch8r
Go goauthentik.io all versions — GO-2025-4137
PyPI authentik-client >= 2025.8.0, < 2025.8.5 · >= 2025.10.0, < 2025.10.2 2025.8.5, 2025.10.2 PYSEC-2025-237

Advisories 2

References