authentik has an insufficient check for account active status during OAuth/SAML authentication

CVE Details

Basic Information

Title authentik has an insufficient check for account active status during OAuth/SAML authentication
Type cve
Published 2025-07-23T20:35:07.243Z
Modified 2025-07-23T20:49:29.415Z

Product Information

Vendor goauthentik
Product authentik
Version <= 2025.4.3, < 2025.4.4

CVSS Information

Base Score 7.1 (HIGH)
Attack Vector CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H

Affected Products

  • goauthentik authentik <= 2025.4.3, < 2025.4.4
  • goauthentik authentik >= 2025.6.0-rc1, < 2025.6.4

Additional Information

CWE List CWE-269
Source GitHub_M

Description

authentik is an open-source Identity Provider that emphasizes flexibility and versatility, with support for a wide set of protocols. In versions 2025.4.4 and earlier, as well as versions 2025.6.0-rc1 through 2025.6.3, deactivated users who registered through OAuth/SAML or linked their accounts to OAuth/SAML providers can still retain partial access to the system despite their accounts being deactivated. They end up in a half-authenticated state where they cannot access the API but crucially they can authorize applications if they know the URL of the application. To workaround this issue, developers can add an expression policy to the user login stage on the respective authentication flow with the expression of return request.context[“pending_user”].is_active. This modification ensures that the return statement only activates the user login stage when the user is active. This issue is fixed in versions authentik 2025.4.4 and 2025.6.4.

💭 Join the Security Discussion

🔒 Your email address will not be published. Required fields are marked *

⚠️ Please be respectful and constructive in your comments. Security discussions should remain professional.