GitLab: Improper Neutralization of Special Elements used in an LDAP Query
CVE-2026-15723 is a high-severity improper neutralization of special elements used in an LDAP query vulnerability in GitLab, with a CVSS 3.1 base score of 8.2 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists versions 19.3.6, 19.4.3, 19.5.1 as the first without the flaw, so updating GitLab to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.54% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update GitLab to 19.3.6 or 19.4.3 or 19.5.1, whichever matches your release line, or a later version.
- Read the advisory on docs.gitlab.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| GitLab | GitLab | 10.1 up to, but not including, 19.3.6; 19.4 up to, but not including, 19.4.3; 19.5 up to, but not including, 19.5.1 | 19.3.6, 19.4.3, 19.5.1 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- HighSuccess depends on conditions outside the attacker's control.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N. Scored by CNA (gitlab.com).
Official description
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Neutralization of Special Elements used in an LDAP Query
The product 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.
More Improper Neutralization of Special Elements used in an LDAP Query vulnerabilities (CWE-90)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Other references
- gitlab.com/gitlab-org/gitlab/-/work_items/605977Permissions Required
- hackerone.com/reports/3852192Permissions Required
Other vulnerabilities in GitLab
- 7.1 High severity
- 7.5 High severity
- 10.0 Critical severity
- 10.0 Critical severity
- 7.3 High severity
- 8.7 High severity
Recent Improper Neutralization of Special Elements used in an LDAP Query vulnerabilities
- 8.8 High severity
- 8.1 High severity
- 9.1 Critical severity
- 7.3 High severity
- 7.1 High severity
- 9.3 Critical severity
Spotted an error? Tell us.