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.
CVE-2026-55106
This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 84% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(medium)
- EG Risk
- 39(Track)EG Risk 39/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity53% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 16%
- KEV
- Not listed
Published
August 18, 2026
Last Modified
August 18, 2026
Advisory Details (5)
Auto-updated Aug 18, 2026LDAP Source debug endpoint accessible without authorization · Advisory · goauthentik/authentik · GitHub
https://github.com/goauthentik/authentik/security/advisories/GHSA-h8ff-c3h7-2gf8security: automated internal backport of patch 1887.sec.patch to authentik-2026.5
Fix merged in goauthentik/authentik PR #24060 on 2026-07-15 — awaiting tagged release
https://github.com/goauthentik/authentik/pull/24060security: automated internal backport of patch 1887.sec.patch to authentik-2026.2
Fix merged in goauthentik/authentik PR #24055 on 2026-07-15 — awaiting tagged release
https://github.com/goauthentik/authentik/pull/24055commit fc336da4bd32 (goauthentik/authentik)
Fix landed in goauthentik/authentik commit fc336da4bd32 — awaiting tagged release
https://github.com/goauthentik/authentik/commit/fc336da4bd32bef52800c77d91aa0b82c5533041commit e638de232174 (goauthentik/authentik)
Fix landed in goauthentik/authentik commit e638de232174 — awaiting tagged release
https://github.com/goauthentik/authentik/commit/e638de23217480854ec5e48ca6fceae479321f99Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× in last 7d / 25× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-30 02:02 UTCEG score recompute
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 03:49 UTCEG score recompute
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-28 02:24 UTCEG score recompute
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-27 04:12 UTCEG score recompute
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-26 06:00 UTCEG score recompute
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 07:48 UTCEG score recompute
- 2026-08-24 09:36 UTCEG score recompute
- 2026-08-23 11:24 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 13:12 UTCEG score recompute
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 15:00 UTCEG score recompute
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-19 18:36 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 20:23 UTCEG score recompute
- 2026-08-18 19:19 UTCEG score recompute
- 2026-08-18 17:21 UTCEG score recompute
- 2026-08-18 17:07 UTCEG score recompute
- 2026-08-18 17:04 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-862
- CVE-2013-3960EG 9.9CRITICAL
- CVE-2015-10143EG 9.8CRITICAL
- CVE-2016-11036EG 9.8CRITICAL
- CVE-2018-11541EG 9.8CRITICAL
- CVE-2011-4183NVD 6.5EG 9.8CRITICAL
- CVE-2018-10251EG 9.8EPSS p90CRITICAL
- CVE-2018-1217EG 9.8EPSS p97CRITICAL
- CVE-2018-0015EG 9.8CRITICAL
- CVE-2017-12582EG 9.8CRITICAL
- CVE-2017-1000056EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-55106?
When was CVE-2026-55106 disclosed?
Is CVE-2026-55106 actively exploited?
What is the CVSS score of CVE-2026-55106?
How do I remediate CVE-2026-55106?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-55106
Is Your Infrastructure Affected by CVE-2026-55106?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.