CVE-2026-94611 json
authentik: Stored credentials are readable with view permission alone
published 2mo ago modified last mo. also BIT-authentik-2026-94611 , EUVD-2026-86277 , GHSA-m9h4-7j9c-55x9
- cvss
- 8.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 27%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- bitnami authentik 2026.2.7, 2026.5.7, 2026.8.2
- goauthentik authentik 2026.2.7, 2026.5.7, 2026.8.2
- github.com/goauthentik/authentik@4b3fad3 commit
- github.com/goauthentik/authentik@5109a4d commit
- github.com/goauthentik/authentik@6bed64e commit
- github.com/goauthentik/authentik@77d2e24 commit
- github.com/goauthentik/authentik#25955 pull request
- github.com/goauthentik/authentik#25960 pull request
- github.com/goauthentik/authentik#25965 pull request
- github.com/goauthentik/authentik#25970 pull request
- github.com/goauthentik/authentik/releases/tag/version/2026.2.7 release
- github.com/goauthentik/authentik/releases/tag/version/2026.5.7 release
Is CVE-2026-94611 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- last mo.
Exploit prediction
0.33% chance of exploitation in the next 30 days, higher than 27% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N |
| OSV | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | authentik | <2026.2.7 >=2026.5.0, <2026.5.7 >=2026.8.0, <2026.8.2 |
2026.2.7 2026.5.7 2026.8.2 |
Affected products
- goauthentik authentik
Classification
References
-
github.com
/goauthentik/authentik/pull/25955
web
-
github.com
/goauthentik/authentik/pull/25960
web
-
github.com
/goauthentik/authentik/pull/25965
web
-
github.com
/goauthentik/authentik/pull/25970
web
-
github.com
/goauthentik/authentik/commit/4b3fad38be44ef3eef1f0baf83e7b3061229eb99
web
-
github.com
/goauthentik/authentik/commit/5109a4d4998d6a5ee399ca3e22ba546231c140c7
web
-
github.com
/goauthentik/authentik/commit/6bed64ef80a4dd21011cce64c41b1e7c5640ecb3
web
-
github.com
/goauthentik/authentik/commit/77d2e24442c3eb6e88010f40aa569a8bfb584f99
web
-
github.com
/goauthentik/authentik/security/advisories/GHSA-m9h4-7j9c-55x9
web, advisory
-
docs.goauthentik.io
/releases/2026.2#fixed-in-202627
web
-
docs.goauthentik.io
/releases/2026.5#fixed-in-202657
web
-
docs.goauthentik.io
/releases/2026.8#fixed-in-202682
web
-
github.com
/goauthentik/authentik/releases/tag/version/2026.2.7
web
-
github.com
/goauthentik/authentik/releases/tag/version/2026.5.7
web
-
github.com
/goauthentik/authentik/releases/tag/version/2026.8.2
web
-
nvd.nist.gov
/vuln/detail/CVE-2026-94611
web
Sources
- CVE List CVE-2026-94611
- NVD CVE-2026-94611
- OSV BIT-authentik-2026-94611
- Maintainer advisory GHSA-m9h4-7j9c-55x9
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of goauthentik/authentik published their own advisory on GitHub. Reviewed sources take precedence over it.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.