CVE-2025-64521

See a problem?
Please try reporting it to the source first.

Source

https://cve.org/CVERecord?id=CVE-2025-64521

Import Source

https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-64521.json

JSON Data

https://api.osv.dev/v1/vulns/CVE-2025-64521

Aliases

Published

2025-11-19T17:03:19.703Z

Modified

2026-03-13T03:41:10.533956Z

Severity

4.8 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N CVSS Calculator

Summary

authentik deactivated service accounts can authenticate to OAuth

Details

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.

Database specific

{
    "cna_assigner": "GitHub_M",
    "cwe_ids": [
        "CWE-289"
    ],
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/64xxx/CVE-2025-64521.json"
}

References

Affected packages

Git / github.com/goauthentik/authentik

Affected ranges

Type: GIT
Repo: https://github.com/goauthentik/authentik
Events: Introduced

f2805b9b8ab423f35d6b2276e72b77594e5fb681

Fixed

b47ed8894c8cc2431a92d5bc47603bca28810ab2

Database specific

source

"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-64521.json"