Description
authentik is an open-source identity provider. Prior to 2026.2.7, 2026.5.7, and 2026.8.2, authentik API serializers return stored credentials when an account has view permission on an affected configuration, even when that account is not authorized to change the configuration or read its secrets. Affected configurations include one-time code delivery by mail or SMS, outbound provisioning targets, device trust integrations, identity sources, the Kubernetes outpost integration, applications using a client or shared secret, and applications using a proxy provider. Deployments are affected when view permission is granted to accounts that are not intended to read these credentials; deployments where every viewer is permitted to read them are not affected. This issue is fixed in versions 2026.2.7, 2026.5.7, and 2026.8.2.
References10
- docs.goauthentik.io/releases/2026.2#fixed-in-202627
- docs.goauthentik.io/releases/2026.5#fixed-in-202657
- docs.goauthentik.io/releases/2026.8#fixed-in-202682
- github.com/goauthentik/authentik/commit/4b3fad38be44ef3eef1f0ba…
- github.com/goauthentik/authentik/commit/5109a4d4998d6a5ee399ca3…
- github.com/goauthentik/authentik/commit/6bed64ef80a4dd21011cce6…
- github.com/goauthentik/authentik/commit/77d2e24442c3eb6e88010f4…
- github.com/goauthentik/authentik/pull/25955
- github.com/goauthentik/authentik/pull/25960
- github.com/goauthentik/authentik/pull/25965
Metrics
- CVSS 3.1
-
8.1
HIGH
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N - EPSS — exploit probability
- 0% percentile: 27 · as of 9 November 2026
- CWE
- CWE-200CWE-522
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.