CVE-2026-94611: authentik: Stored credentials are readable with view permission alone

Published Sep 24, 2026
·
Updated

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.

Affected Software

1 affected component
Authentik Authentik<2026.2.7, <2026.5.7, <2026.8.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade authentik to a version that resolves this vulnerability.

    Fixed in 2026.2.7

Event History

Sep 24, 2026
CVE Published
via MITRE·04:18 PM
Data Sourced
via MITRE·04:18 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who is exposed to this issue?

Deployments are affected only when view permission on an affected configuration is granted to accounts that are not intended to read its stored credentials. Deployments in which every account with view permission is authorized to read those credentials are not affected.

2

What access does an attacker need to retrieve credentials?

An attacker needs an account with view permission on an affected configuration. They do not need permission to modify the configuration or separate authorization to read its secrets.

3

Which configurations may expose stored credentials?

Affected configurations include one-time-code delivery by email 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.

4

Which versions contain the fix?

The issue is fixed in authentik versions 2026.2.7, 2026.5.7, and 2026.8.2.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203