CVE-2025-53942 – goauthentik.io

Package

Manager: go
Name: goauthentik.io
Vulnerable Version: >=0 <0.0.0-20250722122105-7a4c6b9b50f8

Severity

Level: High

CVSS v3.1: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:L/E:U/RL:O/RC:C

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

EPSS: 0.00073 pctl0.22717

Details

Authentik has insufficient check for account active status when authenticating with OAuth/SAML Sources ### 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).

Metadata

Created: 2025-07-22T14:31:12Z
Modified: 2025-07-23T22:15:09Z
Source: https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2025/07/GHSA-9g4j-v8w5-7x42/GHSA-9g4j-v8w5-7x42.json
CWE IDs: ["CWE-269"]
Alternative ID: GHSA-9g4j-v8w5-7x42
Finding: F159
Auto approve: 1