CVE-2025-64521
BaseFortify
Publication date: 2025-11-19
Last updated on: 2025-11-20
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| 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 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 Powered Q&A
Can you explain this vulnerability to me?
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.
How can this vulnerability impact me? :
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.
What immediate steps should I take to mitigate this vulnerability?
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.