CVE-2025-64521: authentik deactivated service accounts can authenticate to OAuth

Published Nov 19, 2025
·
Updated

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.

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.isactive

For more information

If you have any questions or comments about this advisory:

- Email us at security@goauthentik.io.

Other sources

authentik is an open-source Identity Provider. Prior to versions 2025.8.5 and 2025.10.2, 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. 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.

MITRE

Affected Software

4 affected componentsFixes available
Authentik Authentik<2025.8.5, <2025.10.2
go/goauthentik.io<0.0.0-20251119140106-9dbdfc3f1be0
0.0.0-20251119140106-9dbdfc3f1be0
goauthentik Authentik>=2025.8.0<2025.8.5
goauthentik Authentik>=2025.10.0<2025.10.2

Event History

Nov 19, 2025
CVE Published
via MITRE·05:03 PM
Data Sourced
via MITRE·05:03 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Advisory Published
via GitHub·06:13 PM
Data Sourced
via GitHub·06:13 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2025-64521?

CVE-2025-64521 is classified as a high-severity vulnerability due to its potential to allow unauthorized access to service accounts.

2

How do I fix CVE-2025-64521?

To mitigate CVE-2025-64521, upgrade authentik to version 2025.8.5 or 2025.10.2 or later.

3

What versions of authentik are affected by CVE-2025-64521?

CVE-2025-64521 affects authentik versions prior to 2025.8.5 and 2025.10.2.

4

What is the impact of CVE-2025-64521 on OAuth provider authentication?

CVE-2025-64521 can lead to the creation of insecure service accounts during OAuth provider authentication.

5

Is CVE-2025-64521 publicly disclosed?

Yes, CVE-2025-64521 has been publicly disclosed through security advisories.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203