CVE-2026-55106

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (38th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-61061 (ENISA EUVD)Source: ENISA EUVD

5.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 5.3Exploit: None knownExposed services: Not assessed

The CVE record names the fixed release — apply it.

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.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
39
EG Risk 39/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity53% × 45%
Impact severity (EG Severity): CVSS 5.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
38th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.3): severity, escalated by confirmed exploitation. This CVE's 5.3 is its impact severity (EG Severity), not escalated.

EG Severity
5.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 18, 2026

Last Modified

October 22, 2026

Advisory Details (5)

Auto-updated Aug 18, 2026
Fix named in the CVE record. Sources: github_commit, github_pr, github.
GitHub advisoryMentions a patch (unverified)

LDAP Source debug endpoint accessible without authorization · Advisory · goauthentik/authentik · GitHub

https://github.com/goauthentik/authentik/security/advisories/GHSA-h8ff-c3h7-2gf8
GitHub pull request

security: 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/24060
GitHub pull request

security: 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/24055
GitHub commit

commit fc336da4bd32 (goauthentik/authentik)

Fix landed in goauthentik/authentik commit fc336da4bd32 — awaiting tagged release

https://github.com/goauthentik/authentik/commit/fc336da4bd32bef52800c77d91aa0b82c5533041
GitHub commit

commit e638de232174 (goauthentik/authentik)

Fix landed in goauthentik/authentik commit e638de232174 — awaiting tagged release

https://github.com/goauthentik/authentik/commit/e638de23217480854ec5e48ca6fceae479321f99

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 41× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 122 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 22 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  2. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  3. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  4. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  5. 2026-10-30 12:25 UTCOSV refresh
  6. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  7. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  8. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  9. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  10. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  11. 2026-10-25 14:19 UTCEG score recompute
  12. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  13. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  14. 2026-10-22 21:17 UTCEG score recompute
  15. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  16. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  17. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  18. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  19. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  20. 2026-10-18 03:30 UTCEG score recompute
  21. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  22. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  23. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  24. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  25. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
Show 75 more
  1. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  2. 2026-10-12 15:56 UTCEG score recompute
  3. 2026-10-11 19:39 UTCEG score recompute
  4. 2026-10-11 16:54 UTCEG score recompute
  5. 2026-10-11 14:17 UTCEG score recompute
  6. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  7. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  8. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  9. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  10. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  11. 2026-10-07 11:12 UTCEG score recompute
  12. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  13. 2026-10-06 12:53 UTCEG score recompute
  14. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  15. 2026-10-05 14:33 UTCEG score recompute
  16. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  17. 2026-10-03 17:38 UTCEG score recompute
  18. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  19. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  20. 2026-10-02 06:53 UTCEG score recompute
  21. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  22. 2026-10-01 08:00 UTCEG score recompute
  23. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  24. 2026-09-30 09:48 UTCEG score recompute
  25. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  26. 2026-09-29 04:19 UTCEG score recompute
  27. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  28. 2026-09-28 06:07 UTCEG score recompute
  29. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  30. 2026-09-27 07:55 UTCEG score recompute
  31. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  32. 2026-09-25 01:27 UTCEG score recompute
  33. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  34. 2026-09-23 20:19 UTCEG score recompute
  35. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  36. 2026-09-22 20:25 UTCEG score recompute
  37. 2026-09-20 22:21 UTCEG score recompute
  38. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  39. 2026-09-20 00:08 UTCEG score recompute
  40. 2026-09-19 01:56 UTCEG score recompute
  41. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  42. 2026-09-18 03:43 UTCEG score recompute
  43. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  44. 2026-09-17 05:31 UTCEG score recompute
  45. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  46. 2026-09-16 07:18 UTCEG score recompute
  47. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  48. 2026-09-15 09:04 UTCEG score recompute
  49. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  50. 2026-09-14 10:52 UTCEG score recompute
  51. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  52. 2026-09-13 12:40 UTCEG score recompute
  53. 2026-09-11 16:15 UTCEG score recompute
  54. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  55. 2026-09-10 17:46 UTCEG score recompute
  56. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  57. 2026-09-09 19:33 UTCEG score recompute
  58. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  59. 2026-09-07 16:08 UTCEG score recompute
  60. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  61. 2026-09-06 15:27 UTCEG score recompute
  62. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  63. 2026-09-05 17:14 UTCEG score recompute
  64. 2026-09-04 19:01 UTCEG score recompute
  65. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  66. 2026-09-02 21:56 UTCEG score recompute
  67. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  68. 2026-09-01 20:38 UTCEG score recompute
  69. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  70. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  71. 2026-08-31 00:14 UTCEG score recompute
  72. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  73. 2026-08-30 02:02 UTCEG score recompute
  74. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  75. 2026-08-29 03:49 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-55106?
CVE-2026-55106 is a medium-severity vulnerability; its CVE record was published on August 18, 2026. 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…
When was the CVE record for CVE-2026-55106 published?
The CVE record for CVE-2026-55106 was published on August 18, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 22, 2026; the record at its source may have been updated since.
Is CVE-2026-55106 actively exploited?
CVE-2026-55106 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (38th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-55106?
CVE-2026-55106 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-55106?
The CVE record for CVE-2026-55106 names the fix: "This issue is fixed in versions 2026.2.6 and 2026.5.5."

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-55106

Explore →

Is Your Infrastructure Affected by CVE-2026-55106?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.