Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ CVE-2025-64521 — authentik

🟡 CVSS 5.0 — Medium ✅ No Known Exploit CWE-289 OSV
5.0
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

authentik allows a deactivated Service account to authenticate to OAuth

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.

```python

return request.user.is_active

```

For more information

If you have any questions or comments about this advisory:

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is low, an attacker needs administrative privileges on the target. A user must be tricked into taking some action. The scope is changed, meaning a successful attack can affect components beyond the vulnerable one. Rated impact: confidentiality low, integrity low, availability none.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N

  • Attack vector: Network — reachable from anywhere that can route to the service.
  • Attack complexity: Low — the attack works reliably, with no preparation.
  • Privileges required: High — administrative rights are needed first.
  • User interaction: Required — someone has to click, open or visit something.
  • Scope: Changed — a successful attack reaches components beyond the vulnerable one.
  • Confidentiality impact: Low — limited, and the attacker does not choose what is affected.
  • Integrity impact: Low — limited, and the attacker does not choose what is affected.
  • Availability impact: None.

Weakness class

CVE-2025-64521 is classified as CWE-289: 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.

Affected software

CVE-2025-64521 is recorded against 3 packages.

  • authentik
  • authentik-client (from 2025.10.0 up to 2025.10.2)
  • goauthentik.io

Timeline and source

Published on 16 April 2026 and last revised on 13 July 2026. No public exploit is currently recorded for this entry. A vendor advisory or fix has been published. Record sourced from OSV.

References

github.com (Web)
github.com (Web)
nvd.nist.gov (Web)

Other advisories for this package

authentik has other advisories on record. If you are patching this one, these are worth checking on the same host:

Same weakness in other software

These advisories are the same class of weakness (CWE-289: Authentication Bypass by Alternate Name) in other software:

Details

Severity MEDIUM
CVSS Score 5.0
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N
CWE CWE-289
Public Exploit ✅ No
Source OSV
Published 2026-04-16
Updated 2026-08-20
Modified 2026-07-13

Affected Packages

Software From version Fixed in
authentik — —
authentik-client 2025.10.0 2025.10.2
goauthentik.io — —

Similar Threats

Vulnerability Monitoring

Track new vulnerabilities in authentik

CVE-2025-64521 is rated CVSS 5.0 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.

Set Up Free Alerts →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesCVECVE 2025
✓