CVE-2026-55106: goauthentik authentik · Missing Authorization
Affects goauthentik authentikSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium : upgrade to 2026.5.5 or 2026.2.6 when convenient.
Data as of 16 Nov 2026, 20:25 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2026.5.5, 2026.2.6
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 16 Nov 2026.
What to do
Upgrade authentik and goauthentik/authentik to 2026.5.5 or 2026.2.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| goauthentikauthentik | Affected
| Fixed in
|
| goauthentikauthentik | Affected
| Fixed in
|
GitHubgoauthentik/authentikpkg:github/goauthentik/authentikOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
This issue is fixed in authentik versions 2026.2.6 and 2026.5.5. Users should upgrade to at least these versions to remediate the vulnerability. No additional mitigation steps are indicated or required if the system is updated. Deployments without a configured LDAP Source are not affected.
Description
authentik is an open-source identity provider. Prior to 2026.2.6 and 2026.5.5, a diagnostic action on the LDAP Source API does not enforce the object-level read-authorization filter used by the rest of the API. Any party able to reach the API, including an unauthenticated client, can invoke the diagnostic action against a configured LDAP Source. The server then connects to the upstream directory using the source's configured bind credentials and returns a bounded set of directory entries. The response exposes the distinguished names of those entries and the names of the attributes present on them, revealing directory structure, naming conventions, and the existence of specific accounts and groups, but not attribute values. Deployments without a configured LDAP Source are not affected. This issue is fixed in versions 2026.2.6 and 2026.5.5.
References
- github.com/goauthentik/authentik/security/advisories/GHSA-h8ff-c3h7-2gf8 (opens in a new tab)
- github.com/goauthentik/authentik/pull/24055 (opens in a new tab)
- github.com/goauthentik/authentik/pull/24060 (opens in a new tab)
- github.com/goauthentik/authentik/commit/e638de23217480854ec5e48ca6fceae479321f99 (opens in a new tab)
- github.com/goauthentik/authentik/commit/fc336da4bd32bef52800c77d91aa0b82c5533041 (opens in a new tab)
- github.com/goauthentik/authentik/releases/tag/version/2026.2.6 (opens in a new tab)
- github.com/goauthentik/authentik/releases/tag/version/2026.5.5 (opens in a new tab)