In breve
- CVE-2025-53942 è una vulnerabilità ALTO (CVSS 7.4) che riguarda goauthentik.io, authentik (goauthentik).
- Probabilità di sfruttamento nei prossimi 30 giorni (EPSS): 0.58%, superiore al 47.7% delle vulnerabilità.
- Correzione: aggiornare a 0.0.0-20250722122105-7a4c6b9b50f8, 2025.6.4, 2025.4.4 o successiva.
| Package | Affected versions | Patched versions |
|---|
| goauthentik.io Go | < 0.0.0-20250722122105-7a4c6b9b50f8all versions
| 0.0.0-20250722122105-7a4c6b9b50f8
|
| authentik | ≥ 2025.6.0, < 2025.6.4< 2025.4.4
| 2025.6.42025.4.4
|
Description
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
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:
NVD 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.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free