What is the CVSS score of CVE-2026-94611?

CVE-2026-94611 has a CVSS 3.1 base score of 8.1 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N. EPSS exploitation probability: 0.3%.

How to fix or mitigate CVE-2026-94611?

Within 24 hours, inventory all authentik deployments and identify accounts holding view-but-not-change permission on the affected object types (one-time-code delivery by mail or SMS, Google Workspace and Microsoft Entra outbound provisioning targets, endpoint/GDTC device-trust stages, identity sources, the Kubernetes outpost service connection kubeconfig, OAuth2 applications with client or shared secrets, and applications using a proxy provider), and temporarily reduce those view grants where business operations allow. Within 7 days, upgrade all instances to the vendor-released fixed versions - 2026.2.7, 2026.5.7, or 2026.8.2, selecting the maintenance line nearest your current deployment - and treat every secret in the affected configurations as potentially disclosed by rotating mail/SMS OTP delivery credentials, Google Workspace and Microsoft Entra provisioning secrets, identity source bind credentials, the Kubernetes outpost kubeconfig, and all OAuth2 client/shared secrets and proxy provider secrets, then reviewing audit logs for unexpected reads. Within 30 days, validate that no version below the fixed releases remains, re-review role assignments so view permission on secret-bearing objects is granted only to identities already entitled to those secrets, and add monitoring or alerting for future API reads of secret-bearing serializer endpoints.

authentik CVE-2026-94611

EUVD-2026-86277 HIGH

Information Exposure (CWE-200)

2026-09-24 GitHub_M

Information Disclosure Kubernetes Authentik Goauthentik

8.1

CVSS 3.1 · Vendor: GitHub_M

View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

Access

Authenticate as low-privilege account with view permission
Delivery

Request affected config via API serializer endpoint
Exploit

Serializer returns stored secret_fields unredacted
Execution

Harvest kubeconfig/client_secret/shared_secret
Impact

Reuse credentials against backing system

Vulnerability Assessment

Weakness	CWE CWE-200 OWASP Top 10:2025 A01:2025 - Broken Access Control ASVS 5.0 V14 - Data Protection Data exposure prevention MITRE ATT&CK 2 techniques across 2 tactics: Collection, Discovery The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. Sign in to read
Exploitation Conditions	Requires an authenticated authentik account that has been granted VIEW permission (but not change/read-secret permission) on one of the affected configurations: one-time-code mail/SMS delivery, Google Workspace or Microsoft Entra outbound provisioning targets, endpoint (GDTC) device-trust integrations, identity sources, the Kubernetes outpost service connection, OAuth2 applications using a client/shared secret, or applications using a proxy provider. The deployment is ONLY affected when such view permission is delegated to accounts not intended to read secrets - deployments where every viewer is already permitted to read those secrets are NOT affected. This RBAC-delegation prerequisite, plus the need for a valid authenticated account (PR:L), is the primary limiting factor; there is no user-interaction requirement.
Impact	The provided CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N, base 8.1) describes a network-reachable, low-complexity flaw requiring only low privileges - an authenticated authentik account that holds VIEW permission on an affected object. The core impact is confidentiality: the API serializer returned stored secrets (kubeconfig, OAuth2 client_secret, Radius shared_secret, outbound-provisioning credentials, endpoint device-trust credentials) to viewers who were never authorized to read them. I dispute the I:H rating: the direct vulnerability is pure information disclosure (CWE-200), and integrity impact only materializes downstream if an attacker reuses the leaked credentials - so a stricter assessment is C:H/I:N (~6.5). No EPSS score, no CISA KEV listing, and no public exploit are present in the input, so exploitation status is 'no public exploit identified at time of analysis.' Crucially, the vulnerability is conditional: it only affects deployments that grant view permission to accounts NOT intended to read the secrets. In default/single-admin setups where every viewer is already permitted to read secrets, there is no exposure. This makes it a real but configuration-gated priority - most impactful for organizations using authentik's fine-grained RBAC to delegate limited/read-only admin access. Given leaked secrets can include a full Kubernetes kubeconfig, real-world consequences can be severe where the misconfiguration exists.
Exploit ScenarioDerived	In an authentik deployment using delegated RBAC, a low-privileged user (e.g. a help-desk or read-only operator account) is granted view permission on a provider or outpost integration but not permission to change it or read its secrets. That user queries the corresponding API serializer endpoint and receives the stored secret in the response - for example a Kubernetes kubeconfig or an OAuth2 client_secret - which they then reuse to access the backing system. No public exploit code is identified; the attack requires only a standard authenticated API request.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).

Patch available 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 24, 2026

API serializers in authentik return stored credentials to any authenticated account that holds only VIEW permission on an affected configuration, exposing secrets the account was never authorized to read. Affected configurations include one-time-code delivery by mail or SMS, Google Workspace and Microsoft Entra outbound provisioning targets, endpoint (GDTC) device-trust stages, identity sources, the Kubernetes outpost service connection (kubeconfig), OAuth2 applications using a client or shared secret, and applications using a proxy provider; the flaw is fixed in 2026.2.7, 2026.5.7, and 2026.8.2. Exploitation requires an authenticated account (CVSS PR:L) that has been granted view - but not change - permission on one of those objects, so deployments where every viewer is already entitled to read those secrets are not affected; no public exploit code has been identified at time of analysis and there is no confirmed active exploitation (CISA KEV).

RemediationAI

Vendor-released patch: upgrade to authentik 2026.2.7, 2026.5.7, or 2026.8.2 on the matching release branch (tags and notes at https://github.com/goauthentik/authentik/releases/tag/version/2026.2.7, https://github.com/goauthentik/authentik/releases/tag/version/2026.5.7, and https://github.com/goauthentik/authentik/releases/tag/version/2026.8.2; advisory https://github.com/goauthentik/authentik/security/advisories/GHSA-m9h4-7j9c-55x9); the underlying fix is in the upstream PRs 25955, 25960, 25965, and 25970 and commits 4b3fad38be44ef3eef1f0baf83e7b3061229eb99, 5109a4d4998d6a5ee399ca3e22ba546231c140c7, 6bed64ef80a4dd21011cce64c41b1e7c5640ecb3, and 77d2e24442c3eb6e88010f40aa569a8bfb584f99. Until patching is possible, audit RBAC and revoke view permission on one-time-code mail/SMS delivery, outbound provisioning targets (Google Workspace, Microsoft Entra), GDTC device-trust stages, identity sources, Kubernetes outpost service connections, and OAuth2/proxy providers from any account not explicitly intended to read those secrets - note that this can break legitimate read-only administrative and monitoring workflows that rely on those objects, so grant such accounts change permission only where the secret access is acceptable, or move them to a purpose-built, least-privilege role; additionally restrict API reachability of the affected endpoints to trusted administrative networks, since unauthenticated callers cannot reach them. Because serialized secrets may already have been disclosed, treat all credentials on affected objects as potentially compromised and rotate them after upgrading: OAuth2 client secrets and shared secrets, RADIUS shared secrets, Microsoft Entra client secrets, Google Workspace service credentials, GDTC endpoint credentials, Kubernetes outpost kubeconfigs, identity-source credentials, and SMS/mail one-time-code delivery credentials; rotation is disruptive to configured integrations and outposts and should be staged, but is the only way to invalidate material that a view-only account may have read.

Affected VersionsENISA

authentik 2026.8.0, < 2026.8.2

authentik 2026.5.0, < 2026.5.7

authentik < 2026.2.7

Affected Packages

euvd authentik fix: 2026.2.7, 2026.5.7, 2026.8.2

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

authentik is a Django-based open-source identity provider whose REST API is built on Django REST Framework serializers. The underlying defect is CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor): serializers backed by the shared ModelSerializer in authentik/core/api/utils.py emitted every field of a model on read, including credential-bearing fields, without checking whether the requesting user held the model's change permission. Because the API permission model gates serialization on view permission while the credentials are only meant to be readable by users who may modify the object, a plain viewer received secrets in the serialized representation. The fix introduces a secret_fields Meta attribute and overrides to_representation() to strip those fields unless request.user.has_perm("<app>.change_<model>", instance) returns true; the PR series marks the Google Workspace credentials field, the GDTC endpoint credentials field, the Kubernetes outpost service-connection kubeconfig, the OAuth2 client_secret, and the RADIUS shared_secret as secret fields, and converts the Microsoft Entra client_secret to DRF write_only. The same patch set hardens adjacent endpoints by adding IsOutpostServiceAccount and IsOutpostDelegatedRequest permission classes (keyed on the ak-outpost- service-account username prefix) to the proxy outpost config and RADIUS outpost config viewsets. Affected identifiers correspond to CPE cpe:2.3:a:goauthentik:authentik and ENISA EUVD-2026-86277.

Know when Authentik gets its next vulnerability

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

Vendor (GitHub_M) PRIMARY 8.1 HIGH

AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

vuln.today AI 6.5 MEDIUM

Network API access with a low-priv authenticated view-only account (PR:L); pure credential disclosure gives C:H, while integrity/availability are only downstream via credential reuse, so I:N/A:N.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (GitHub_M).

CVSS VectorVendor: GitHub_M

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

None

Lifecycle Timeline

Patch available

Sep 24, 2026 - 17:03 EUVD

CVE Published

Sep 24, 2026 - 16:18 cve.org

HIGH 8.1

DescriptionCVE.org

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.

Technical POC Analysis

Bug class: exposure of sensitive information to an unauthorized actor (CWE-200), with CWE-522 (insufficiently protected credentials) as the secondary weakness recorded in the advisory.

Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.

Executive ViewAI

Why It Matters

authentik's API is exposing stored secrets - mail/SMS one-time-code delivery credentials, Google Workspace and Microsoft Entra provisioning secrets, device-trust stages, identity sources, Kubernetes kubeconfigs, and OAuth2/proxy application secrets - to any authenticated account holding view-only rights on those objects. This means users who were deliberately denied change or reveal privileges can still read live credentials, opening the door to lateral movement into downstream identity and cloud environments governed by authentik. Leadership should care because the exposed material is exactly what protects authentication and provisioning pathways, so a single over-permissioned viewer account can quietly undermine the trust anchor for the whole organization.

Business Impact: High

Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score

0.3%

Top 76% exploitable

Prevalence

Medium

popular self-hosted open-source identity provider, common but not ubiquitous

Data Quality

5 sources

Confidence: Medium

EUVD

NVD

CVE.org

EPSS

Vulnrichment

GitHub

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity HIGH

CISA KEV No

Public POC No

EPSS 0.3%

Patch available Yes

Active threat No

Deciding rule

HIGH severity (CVSS 7.0-8.9)

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision

Scheduled

Exploitation

None

System Exposure· derived

Open

Automatable

Human Impact

High

Technical Impact

Total

Priority Score

Low Medium High Critical

KEV: 0

EPSS: 0

CVSS: +40

PoC: 0

Weaponized: 0

Threat intel: 0

Gov advisory: 0

Attack Technique

Information Disclosure MEDIUM

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.