Skip to main content
CVE-2025-53942VulnerabilityPublished

CVE-2025-53942: goauthentik authentik · Improper Privilege Management

Affects goauthentik authentikSource CVE Database V5

0

Not known to be exploited · CVSS 7.1 High · fixed in 2025.4.4 : patch goauthentik authentik soon.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2025.4.4
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
Gogithub.com/goauthentik/authentikpkg:golang/github.com/goauthentik/authentikOther threatsAffected
  • <=2025.4.4
  • >=2025.6.0 <=2025.6.3
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should promptly upgrade authentik deployments to versions 2025.4.4 or 2025.6.4 where the vulnerability is fixed. Until upgrades are feasible, administrators should implement the recommended expression policy in the user login stage to verify user active status explicitly, preventing deactivated users from proceeding in the authentication flow. Additionally, organizations should audit existing deactivated accounts linked via OAuth/SAML to identify any that might be in the half-authenticated state and revoke or reset their credentials. Monitoring authentication logs for unusual authorization activity related to deactivated users is advised. Integrating multi-factor authentication (MFA) and strict session management policies can further reduce risk. Finally, organizations should review their identity lifecycle management processes to ensure timely and complete deactivation of user access across all integrated systems.

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.

References

Community reviews

Loading reviews…