goauthentik up to 2026.2.6/2026.5.6/2026.8.1 API serializers improper authorization

Summaryinfo

A vulnerability was found in goauthentik authentik up to 2026.2.6/2026.5.6/2026.8.1. It has been classified as problematic. Affected is an unknown function of the component API serializers. Performing a manipulation results in improper authorization. This vulnerability is reported as CVE-2026-94611. The attack is possible to be carried out remotely. No exploit exists. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability classified as problematic has been found in goauthentik authentik up to 2026.2.6/2026.5.6/2026.8.1. This affects an unknown code block of the component API serializers. The manipulation with an unknown input leads to a improper authorization vulnerability. CWE is classifying the issue as CWE-285. The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. This is going to have an impact on confidentiality. The summary by CVE is:

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.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-94611 since 09/21/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1548.002 for this issue.

Upgrading to version 2026.2.7, 2026.5.7 or 2026.8.2 eliminates this vulnerability.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• goauthentik

Name

• authentik

Version

• 2026.2.0
• 2026.2.1
• 2026.2.2
• 2026.2.3
• 2026.2.4
• 2026.2.5
• 2026.2.6
• 2026.5.0
• 2026.5.1
• 2026.5.2
• 2026.5.3
• 2026.5.4
• 2026.5.5
• 2026.5.6
• 2026.8.0
• 2026.8.1

Website

• Product: https://github.com/goauthentik/authentik/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion