CVE-2025-53942
authentik has an insufficient check for account active status during OAuth/SAML authentication
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 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.
How to fix CVE-2025-53942
To remediate CVE-2025-53942, upgrade the affected package to a fixed version below.
- —upgrade to 2025.4.4 or later
- —upgrade to 0.0.0-20250722122105-7a4c6b9b50f8 or later
- —no fix listed
Is CVE-2025-53942 being exploited?
Low — EPSS is 0.2%, meaning exploitation activity has not been observed at scale.
Affected packages (3)
- from 0, < 2025.4.4, >= 2025.6.0, < 2025.6.4
- from 0, < 0.0.0-20250722122105-7a4c6b9b50f8
- from 0
CVSS scores
| Source | Version | Severity | Vector |
|---|---|---|---|
| osv | CVSS 4.0 | — | 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 |