Skip to content

authentik allows a deactivated Service account to authenticate to OAuth

Moderate severity GitHub Reviewed Published Nov 19, 2025 in goauthentik/authentik • Updated Nov 19, 2025

Package

gomod goauthentik.io (Go)

Affected versions

< 0.0.0-20251119140106-9dbdfc3f1be0

Patched versions

0.0.0-20251119140106-9dbdfc3f1be0

Description

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

@BeryJu BeryJu published to goauthentik/authentik Nov 19, 2025
Published by the National Vulnerability Database Nov 19, 2025
Published to the GitHub Advisory Database Nov 19, 2025
Reviewed Nov 19, 2025
Last updated Nov 19, 2025

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(5th percentile)

Weaknesses

Incorrect User Management

The product does not properly manage a user within its environment. Learn more on MITRE.

Authentication Bypass by Alternate Name

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. Learn more on MITRE.

CVE ID

CVE-2025-64521

GHSA ID

GHSA-xr73-jq5p-ch8r

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.