{"id":"EUVD-2025-198186","enisaUuid":"8a060522-5c69-38ff-bfa8-81468d6bebc9","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.","datePublished":"Nov 19, 2025, 5:03:19 PM","dateUpdated":"Nov 19, 2025, 9:09:40 PM","baseScore":4.8,"baseScoreVersion":"3.1","baseScoreVector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N","references":"https://github.com/goauthentik/authentik/security/advisories/GHSA-xr73-jq5p-ch8r\nhttps://github.com/goauthentik/authentik/commit/9dbdfc3f1be0f1be36f8efce2442897b2a54a71c\n","aliases":"CVE-2025-64521\nGHSA-xr73-jq5p-ch8r\n","assigner":"GitHub_M","epss":0.23,"enisaIdProduct":[{"id":"a6bb1ec6-da2b-319c-83f3-c77f06626e00","product":{"name":"authentik","vendor":{"name":"goauthentik"}},"product_version":"\u003c 2025.10.2"},{"id":"fdb0261a-918a-31b5-83c2-a5c4b6b18706","product":{"name":"authentik","vendor":{"name":"goauthentik"}},"product_version":"\u003c 2025.8.5"}],"enisaIdVendor":[{"id":"7ffac464-fbbe-3f84-8f5e-60c46857f26c","vendor":{"name":"goauthentik"}}],"enisaIdVulnerability":[{"id":"1165fdbf-37d7-329a-ba86-2272e08afed6","vulnerability":{"id":"GHSA-xr73-jq5p-ch8r","description":"authentik allows a deactivated Service account to authenticate to OAuth","datePublished":"Nov 19, 2025, 6:13:03 PM","dateUpdated":"Nov 19, 2025, 6:59:53 PM","baseScore":0.0,"references":"https://github.com/goauthentik/authentik/security/advisories/GHSA-xr73-jq5p-ch8r\nhttps://nvd.nist.gov/vuln/detail/CVE-2025-64521\nhttps://github.com/goauthentik/authentik/commit/9dbdfc3f1be0f1be36f8efce2442897b2a54a71c\nhttps://github.com/goauthentik/authentik\n","enisa_id":"EUVD-2025-198186\n","aliases":"GHSA-xr73-jq5p-ch8r\nCVE-2025-64521\n","epss":0.0,"dataProcessed":"Nov 1, 2026, 1:56:19 AM","vulnerabilityProduct":[],"vulnerabilityVendor":[]}},{"id":"679d093f-027f-334e-a7bd-2f5f8d911d39","vulnerability":{"id":"PYSEC-2025-237","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.","datePublished":"Nov 19, 2025, 5:15:52 PM","dateUpdated":"Jul 13, 2026, 5:48:01 AM","baseScore":0.0,"references":"https://github.com/goauthentik/authentik/commit/9dbdfc3f1be0f1be36f8efce2442897b2a54a71c\nhttps://github.com/goauthentik/authentik/security/advisories/GHSA-xr73-jq5p-ch8r\n","enisa_id":"EUVD-2025-198186\n","aliases":"CVE-2025-64521\nGHSA-xr73-jq5p-ch8r\n","epss":0.0,"dataProcessed":"Nov 1, 2026, 2:10:30 AM","vulnerabilityProduct":[],"vulnerabilityVendor":[]}},{"id":"8421d921-8abf-3d76-96c7-dc9113608fff","vulnerability":{"id":"CVE-2025-64521","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.","datePublished":"Nov 19, 2025, 5:03:19 PM","dateUpdated":"Nov 19, 2025, 9:09:40 PM","status":"PUBLISHED","baseScore":4.8,"baseScoreVersion":"3.1","baseScoreVector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N","references":"https://github.com/goauthentik/authentik/security/advisories/GHSA-xr73-jq5p-ch8r\nhttps://github.com/goauthentik/authentik/commit/9dbdfc3f1be0f1be36f8efce2442897b2a54a71c\n","enisa_id":"EUVD-2025-198186\n","assigner":"GitHub_M","epss":0.23,"dataProcessed":"Nov 2, 2026, 7:20:56 AM","vulnerabilityProduct":[{"id":"bec5b332-2417-3b53-baaf-65e3bdf5f126","product":{"name":"authentik","vendor":{"name":"goauthentik"}},"product_version":"\u003c 2025.10.2"},{"id":"e7ffff9e-245e-39b3-ab96-1b20d65b7a29","product":{"name":"authentik","vendor":{"name":"goauthentik"}},"product_version":"\u003c 2025.8.5"}],"vulnerabilityVendor":[{"id":"40d211a1-b35b-3c30-aa48-1b4e171b087f","vendor":{"name":"goauthentik"}}]}}],"enisaIdAdvisory":[]}