LDAP Injection in GitLab
CVE-2026-15723
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 10.1 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1 that, when OmniAuth SAML and LDAP auto-linking were both enabled, an authenticated user could have taken over an existing LDAP-backed account without any interaction from the targeted user, due to improper input sanitization in the LDAP email lookup path used during OmniAuth identity linking.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 8.2 (High). Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N.
EPSS exploit prediction
No EPSS score from FIRST.org yet. New CVEs usually get one within a few days; no score means no signal yet, not low risk. How EPSS works.
Affected products
Weakness classification (CWE)
References
- gitlab.com/gitlab-org/gitlab/-/work_items/605977
- hackerone.com/reports/3852192 (technical-description, permissions-required, exploit)
- docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-1-released/
Frequently asked questions
- What is CVE-2026-15723?
- CVE-2026-15723 is a high-severity vulnerability in GitLab, classified under LDAP Injection. CVSS score: 8.2/10. Published 2026-10-22.
- How severe is CVE-2026-15723?
- High severity. CVSS v3 base score is 8.2 out of 10.