CVE-2025-64521
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-11-19

Last updated on: 2025-11-20

Assigner: GitHub, Inc.

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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-11-19
Last Modified
2025-11-20
Generated
2026-06-16
AI Q&A
2025-11-19
EPSS Evaluated
2026-06-15
NVD
CVE-2025-64521
EUVD
EUVD-2025-198186
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
goauthentik authentik From 2025.8.0 (inc) to 2025.8.5 (exc)
goauthentik authentik From 2025.10.0 (inc) to 2025.10.2 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-289 The product performs authentication based on the name of a resource being accessed, or the name of the actor performing the access, but it does not properly check all possible names for that resource or actor.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability in authentik occurs because service accounts created for OAuth providers could still be authenticated even after being deactivated. This means that although other permissions and policies are correctly enforced, the deactivated service account could still be used to authenticate, potentially allowing unauthorized access. The issue is fixed in versions 2025.8.5 and 2025.10.2, and a workaround is to add a policy that explicitly checks if the service account is still valid and denies access if it is not.

Impact Analysis

The vulnerability can allow a deactivated service account to still authenticate, which may lead to unauthorized access to systems or data that rely on authentik for identity management. This could result in potential information disclosure or misuse of privileges, although other permissions and policies are still enforced correctly.

Mitigation Strategies

Upgrade authentik to version 2025.8.5 or 2025.10.2 where the issue is fixed. As a workaround, add a policy to the application that explicitly checks if the service account is still valid and deny access if it is not.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2025-64521. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart