GitLab CE/EE LDAP Takeover via OmniAuth SAML/LDAP Auto-linking (19.5.1)
CVE-2026-15723 Published on October 21, 2026

Improper Neutralization of Special Elements used in an LDAP Query ('LDAP Injection') in GitLab
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.

NVD

Vulnerability Analysis

CVE-2026-15723 can be exploited with network access, and requires small amount of user privileges. This vulnerability is consided to have a high level of attack complexity. The potential impact of an exploit of this vulnerability is considered to have a high impact on confidentiality and integrity, and no impact on availability.

Attack Vector:
NETWORK
Attack Complexity:
HIGH
Privileges Required:
LOW
User Interaction:
NONE
Scope:
CHANGED
Confidentiality Impact:
HIGH
Integrity Impact:
HIGH
Availability Impact:
NONE

Weakness Type

What is a LDAP Injection Vulnerability?

The software constructs all or part of an LDAP query using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended LDAP query when it is sent to a downstream component.

CVE-2026-15723 has been classified to as a LDAP Injection vulnerability or weakness.


Products Associated with CVE-2026-15723

Want to know whenever a new CVE is published for GitLab? stack.watch will email you.

 

Affected Versions

GitLab: