authentik: Exposure of Sensitive Information to an Unauthorized Actor
CVE-2026-94611 is a high-severity exposure of sensitive information to an unauthorized actor vulnerability in authentik from Goauthentik, with a CVSS 3.1 base score of 8.1 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. Affected authentik versions: < 2026.2.7; >= 2026.5.0, < 2026.5.7; >= 2026.8.0, < 2026.8.2. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.33% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of authentik you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on github.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Goauthentik | authentik | < 2026.2.7; >= 2026.5.0, < 2026.5.7; >= 2026.8.0, < 2026.8.2 | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N. Scored by CNA (github.com).
Official 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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Exposure of Sensitive Information to an Unauthorized Actor
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
How developers prevent this class of flaw
- Compartmentalize the system to have safe areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
More Exposure of Sensitive Information to an Unauthorized Actor vulnerabilities (CWE-200)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
References
Patches and release notes
- 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/4b3fad38be44ef3eef1f0baf83e7b3061229eb99
- github.com/goauthentik/authentik/commit/5109a4d4998d6a5ee399ca3e22ba546231c140c7
- github.com/goauthentik/authentik/commit/6bed64ef80a4dd21011cce64c41b1e7c5640ecb3
- github.com/goauthentik/authentik/commit/77d2e24442c3eb6e88010f40aa569a8bfb584f99
- github.com/goauthentik/authentik/pull/25955
- github.com/goauthentik/authentik/pull/25960
- github.com/goauthentik/authentik/pull/25965
- github.com/goauthentik/authentik/pull/25970
- github.com/goauthentik/authentik/releases/tag/version/2026.2.7
- github.com/goauthentik/authentik/releases/tag/version/2026.5.7
- github.com/goauthentik/authentik/releases/tag/version/2026.8.2
Other vulnerabilities in authentik
- 7.5 High severity
- 7.4 High severity
- 8.8 High severity
- 8.9 High severity
- 8.8 High severity
- 9.4 Critical severity
Recent Exposure of Sensitive Information to an Unauthorized Actor vulnerabilities
- 7.5 High severity
- 7.5 High severity
- 8.6 High severity
- 8.2 High severity
- 7.7 High severity
- 7.3 High severity
Spotted an error? Tell us.