Skip to main content
VulnerabilityPublished

CVE-2026-94611: goauthentik authentik · Information Exposure

Affects goauthentik authentikSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.1 High · fixed in 2026.8.2 : patch goauthentik authentik soon.

Data as of 8 Nov 2026, 23:24 UTC

CVSS 3.1 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2026.8.2, 2026.5.7, 2026.2.7
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.

What to do

Upgrade authentik and goauthentik/authentik to 2026.8.2, 2026.5.7 or 2026.2.7.

Affected software

ProductAffectedFixed in
goauthentikauthentikAffected
  • >=2026.8.0 <2026.8.2
Fixed in
  • 2026.8.2
goauthentikauthentikAffected
  • >=2026.5.0 <2026.5.7
Fixed in
  • 2026.5.7
goauthentikauthentikAffected
  • <2026.2.7
Fixed in
  • 2026.2.7
GitHubgoauthentik/authentikpkg:github/goauthentik/authentikOther threatsAffected
  • <2026.2.7
  • >=2026.5.0 <2026.5.7
  • >=2026.8.0 <2026.8.2
Fixed in
  • 2026.2.7
  • 2026.5.7
  • 2026.8.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade authentik to version 2026.2.7, 2026.5.7, or 2026.8.2 or later to apply the official fix. Restrict view permissions on affected configurations to only those accounts authorized to access stored credentials until the update is applied.

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.

References

Community reviews

Loading reviews…