CVE-2026-94611
authentik: Stored credentials are readable with view permission alone
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.
INFO
Published Date :
Sept. 24, 2026, 5:17 p.m.
Last Modified :
Sept. 24, 2026, 5:17 p.m.
Remotely Exploit :
Yes !
Source :
[email protected]
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | HIGH | [email protected] |
Solution
- Update authentik to version 2026.2.7 or later.
- Update authentik to version 2026.5.7 or later.
- Update authentik to version 2026.8.2 or later.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-94611.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-94611 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-94611
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-94611 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-94611 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by [email protected]
Sep. 24, 2026
Action Type Old Value New Value Added 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. Added CVSS V3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N Added CWE CWE-200 Added CWE CWE-522 Added Affected New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/94xxx/CVE-2026-94611.json">CVE-2026-94611</a> Added Reference https://docs.goauthentik.io/releases/2026.2#fixed-in-202627 Added Reference https://docs.goauthentik.io/releases/2026.5#fixed-in-202657 Added Reference https://docs.goauthentik.io/releases/2026.8#fixed-in-202682 Added Reference https://github.com/goauthentik/authentik/commit/4b3fad38be44ef3eef1f0baf83e7b3061229eb99 Added Reference https://github.com/goauthentik/authentik/commit/5109a4d4998d6a5ee399ca3e22ba546231c140c7 Added Reference https://github.com/goauthentik/authentik/commit/6bed64ef80a4dd21011cce64c41b1e7c5640ecb3 Added Reference https://github.com/goauthentik/authentik/commit/77d2e24442c3eb6e88010f40aa569a8bfb584f99 Added Reference https://github.com/goauthentik/authentik/pull/25955 Added Reference https://github.com/goauthentik/authentik/pull/25960 Added Reference https://github.com/goauthentik/authentik/pull/25965 Added Reference https://github.com/goauthentik/authentik/pull/25970 Added Reference https://github.com/goauthentik/authentik/releases/tag/version/2026.2.7 Added Reference https://github.com/goauthentik/authentik/releases/tag/version/2026.5.7 Added Reference https://github.com/goauthentik/authentik/releases/tag/version/2026.8.2 Added Reference https://github.com/goauthentik/authentik/security/advisories/GHSA-m9h4-7j9c-55x9