NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · Go

CVE-2025-64521: authentik allows a deactivated Service account to authenticate to OAuth

mediumCVSS 3.1 4.8GHSA-xr73-jq5p-ch8r

Summary When authenticating with clientid and clientsecret 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.

Published Nov 19, 2025

Affected packages

goauthentik.io

Ecosystem
Go
Affected
< 0.0.0-20251119140106-9dbdfc3f1be0
Fixed in
0.0.0-20251119140106-9dbdfc3f1be0
Check
go list -m goauthentik.io

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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:

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More Go vulnerabilities

All Go entries