GitHub Advisoryadvisory · Go

GHSA-xr73-jq5p-ch8r authentik allows a deactivated Service account to authenticate to OAuth

MEDIUM Published 2025-11-19 Modified 2025-11-19 Official page ↗
Aliases
CVE-2025-64521
Ecosystem
Go
Packages
goauthentik.io
Severity
Moderate
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N
Weaknesses
CWE-286, CWE-289
Reviewed
2025-11-19

Affected packages

• Go goauthentik.io: < 0.0.0-20251119140106-9dbdfc3f1be0 → fixed in 0.0.0-20251119140106-9dbdfc3f1be0

Description

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. ```python return request.user.is_active ``` For more information If you have any questions or comments about this advisory: • Email us at [email protected].

Related

Alias · CVE (1)

  • CVE-2025-64521 authentik is an open-source Identity Provider. vulnerability

Weakness · CWE (2)

  • CWE-286 Incorrect User Management weakness
  • CWE-289 Authentication Bypass by Alternate Name weakness

References