GHSA-xr73-jq5p-ch8r

Suggest an improvement
Source
https://github.com/advisories/GHSA-xr73-jq5p-ch8r
Import Source
https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2025/11/GHSA-xr73-jq5p-ch8r/GHSA-xr73-jq5p-ch8r.json
JSON Data
https://api.test.osv.dev/v1/vulns/GHSA-xr73-jq5p-ch8r
Aliases
Published
2025-11-19T18:13:03Z
Modified
2025-11-19T18:59:53Z
Severity
  • 4.8 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N CVSS Calculator
Summary
authentik allows a deactivated Service account to authenticate to OAuth
Details

Summary

When authenticating with client_id and client_secret to an OAuth provider, authentik creates a service account for the provider. In previous authentik versions, authentication for this account was possible even when the account was deactivated. Other permissions are correctly applied and federation with other providers still take assigned policies correctly into account.

Patches

authentik 2025.8.5 and 2025.10.2 fix this issue, for other versions the workaround below can be used.

Workarounds

You can add a policy to your application that explicitly checks if the service account is still valid, and deny access if not.

return request.user.is_active

For more information

If you have any questions or comments about this advisory:

Database specific 
{
    "severity": "MODERATE",
    "cwe_ids": [
        "CWE-286",
        "CWE-289"
    ],
    "nvd_published_at": "2025-11-19T17:15:52Z",
    "github_reviewed_at": "2025-11-19T18:13:03Z",
    "github_reviewed": true
}
References

Affected packages

Go / goauthentik.io

Package

Name
goauthentik.io
View open source insights on deps.dev
Purl
pkg:golang/goauthentik.io

Affected ranges

Type
SEMVER
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
0.0.0-20251119140106-9dbdfc3f1be0