https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-03T20:57:40.205172+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bit-authentik-2025-53942 BIT-authentik-2025-53942 — authentik has an insufficient check for account active status during OAuth/SAML authentication 2026-10-03T20:57:40.268715+00:00

Affected: Bitnami: authentik

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 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.

 https://cve.radiocsirt.org/vuln/euvd-2026-248369 EUVD-2026-248369 2026-10-03T20:57:40.268777+00:00 EUVD-2026-248369 https://cve.radiocsirt.org/vuln/fkie_cve-2025-53942 fkie_cve-2025-53942 2026-10-03T20:57:40.268794+00:00

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.

 https://cve.radiocsirt.org/vuln/ghsa-9g4j-v8w5-7x42 GHSA-9g4j-v8w5-7x42 — Authentik has insufficient check for account active status when authenticating with OAuth/SAML Sources 2026-10-03T20:57:40.268823+00:00

Affected: Go: goauthentik.io

### Summary

Deactivated users that had either enrolled via OAuth/SAML or had their account connected to an OAuth/SAML account can still partially access authentik even if their account is 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.

### Patches

authentik 2025.4.4 and 2025.6.4 fix this issue.

### Workarounds

Adding an expression policy to the user login stage on the respective authentication flow with the expression of

```py return request.context["pending_user"].is_active ```

This expression will only activate the user login stage when the user is active.

### For more information

If you have any questions or comments about this advisory:

- Email us at [security@goauthentik.io](mailto:security@goauthentik.io).

 https://cve.radiocsirt.org/vuln/opensuse-su-2025:15434-1 openSUSE-SU-2025:15434-1 — govulncheck-vulndb-0.0.20250811T192933-1.1 on GA media 2026-10-03T20:57:40.268854+00:00

govulncheck-vulndb-0.0.20250811T192933-1.1 on GA media