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.
Fix
Patch, vendor advisory and mitigation references on NVD 1
- https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-1-released/ Release Notes, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 10
- Cpes+4 CPE criteria (now 4)NVD modified 2026-10-27 14:09
- StatusPublished → AnalyzedNVD modified 2026-10-27 14:09
- StatusUndergoing Analysis → PublishedNVD modified 2026-10-23 10:58
- StatusPublished → Undergoing AnalysisNVD modified 2026-10-23 12:18
- StatusUndergoing Analysis → PublishedNVD modified 2026-10-23 03:55
- StatusAwaiting Analysis → Undergoing AnalysisNVD modified 2026-10-23 04:18
- StatusReceived → Awaiting AnalysisNVD modified 2026-10-22 16:18
- Cpes-1 CPE criteria (now 0)NVD modified 2026-10-22 01:16
- StatusPublished → ReceivedNVD modified 2026-10-22 01:16
- First seenCVSS 8.2 · gitlabNVD modified 2026-10-21 23:35
Affected (CPE criteria) 4
cpe:2.3:a:gitlab:gitlab:*:*:*:*:community:*:*:*cpe:2.3:a:gitlab:gitlab:*:*:*:*:enterprise:*:*:*cpe:2.3:a:gitlab:gitlab:19.5.0:*:*:*:community:*:*:*cpe:2.3:a:gitlab:gitlab:19.5.0:*:*:*:enterprise:*:*:*
References 3
- https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-1-released/ Release Notes, Vendor Advisory
- https://gitlab.com/gitlab-org/gitlab/-/work_items/605977 Permissions Required
- https://hackerone.com/reports/3852192 Permissions Required