CVE-2025-64521: GO-2025-4137 - authentik allows a deactivated Service account to authenticate to OAuth in goauthentik.io

CVE-2025-64521 · Severity: medium · CVSS 4.8 · Published 2025-11-19

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.

Technologies: goauthentik.io (Go), Goauthentik Authentik. Vendors: Go, Goauthentik, PyPI.

Quick answers

Is CVE-2025-64521 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2025-64521 being exploited in the wild.
How severe is CVE-2025-64521?
Medium severity, with a CVSS score of 4.8, published 19 November 2025.
Which products and versions are affected?
goauthentik.io (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=0.0.0-20251119140106-9dbdfc3f1be0; authentik-client (PyPI) ECOSYSTEM:introduced=2025.8.0,fixed=2025.8.5,introduced=2025.10.0,fixed=2025.10.2.
Is there a fix for CVE-2025-64521?
Yes. goauthentik.io (Go): upgrade to 0.0.0-20251119140106-9dbdfc3f1be0 or later; authentik-client (PyPI): upgrade to 2025.10.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2025-64521?
Check whether you run goauthentik.io (Go), Goauthentik Authentik or authentik-client (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • goauthentik.io (Go): upgrade to 0.0.0-20251119140106-9dbdfc3f1be0 or later
    go get goauthentik.io@v0.0.0-20251119140106-9dbdfc3f1be0
  • authentik-client (PyPI): upgrade to 2025.10.2 or later
    pip install "authentik-client>=2025.10.2"

Affected products

  • goauthentik.io (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=0.0.0-20251119140106-9dbdfc3f1be0
  • Goauthentik Authentik
  • authentik-client (PyPI) ECOSYSTEM:introduced=2025.8.0,fixed=2025.8.5,introduced=2025.10.0,fixed=2025.10.2

Identifiers

  • CVE-2025-64521
  • GHSA-xr73-jq5p-ch8r
  • GO-2025-4137
  • PYSEC-2025-237

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.