Advisory record · GHSA-9g4j-v8w5-7x42

Authentik has insufficient check for account active status when authenticating with OAuth/SAML Sources

CVSS 7.1 HighEPSS 0.0058 · 48th percentile

Published by the GitHub Advisory Database at 22 Jul 2025, 14:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
goauthentik.ioGo<0.0.0-20250722122105-7a4c6b9b50f80.0.0-20250722122105-7a4c6b9b50f8
Identifiers
GHSA-9g4j-v8w5-7x42 · BIT-authentik-2025-53942 · CVE-2025-53942 · GO-2025-3822
Weakness (CWE)
CWE-269
Published
22 Jul 2025
Updated
17 Apr 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Authentik (goauthentik.io Go module) versions before 0.0.0-20250722122105-7a4c6b9b50f8 are affected. Deactivated users who enrolled via OAuth or SAML, or who have an OAuth or SAML account connected, can still partly sign in and authorize applications if they know the application's URL, though they cannot use the API. Upgrade to 0.0.0-20250722122105-7a4c6b9b50f8 or later; the source also lists authentik 2025.4.4 and 2025.6.4 as fixed releases. A workaround is to add an expression policy to the user login stage that only allows login for active users.

Written 7 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.1 High 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 CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0058, the 48th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:08 UTC First seen by agentprime
  2. 31 Oct 2026, 15:08 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.