CVE Tools

CVE-2026-15723

Improper Neutralization of Special Elements used in an LDAP Query ('LDAP Injection') in GitLab

No known exploitation. EPSS puts it in the 46th percentile. Fixed versions are out.

Check it yourself

No ready-made check. Neither Nuclei nor OpenVAS has one for this CVE yet.

Request a scan

Published Updated Sources: CVE.org, NVD

What to do

Find your product and version, then upgrade to the build on the right.

  • GitLabAffected: ≥ 10.1, < 19.3.6Upgrade to: 19.3.6Affected: ≥ 19.4, < 19.4.3Upgrade to: 19.4.3Affected: ≥ 19.5, < 19.5.1Upgrade to: 19.5.1Stated by: CVE record

Versions as the sources state them. Full version matrix after sign-in

Steps

Written by AI from the record
  1. Check whether your GitLab instance has both OmniAuth SAML and LDAP auto-linking enabled — if not, you are not exposed to this issue.
  2. Check your GitLab version against the ranges: 10.1 up to 19.3.6, 19.4.x before 19.4.3, and 19.5.x before 19.5.1.
  3. Upgrade GitLab to 19.3.6, 19.4.3, or 19.5.1 (or later).
  4. After upgrading, review user accounts for any unexpected changes in LDAP/SAML identity linking.

What it is

From the CVE record

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.

In plain language

Written by AI from the record

A flaw in GitLab could let a logged-in attacker hijack someone else's account under specific login settings, but there's no sign anyone is exploiting it yet, so update soon rather than in a panic.

LDAP injection (CWE-90) in GitLab's OmniAuth SAML-to-LDAP identity linking lets an authenticated attacker take over an existing LDAP-backed account with no victim interaction, when SAML and LDAP auto-linking are both enabled; fixed in 19.3.6, 19.4.3, 19.5.1.

If you're affected

  • Account takeover of other employees
  • Unauthorized access to internal repositories
  • Source code exposure
  • Impersonation of legitimate users

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS46th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.5% chance of exploitation activity in the next 30 days, which ranks it in the 46th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

11 events over 14 days, from the signal feeds we watch.

  1. Patch availablerecord updated
  2. Patch availablerecord updated
  3. Patch availablerecord updated
  4. Patch availablerecord updated
  5. Patch availablepublished, weakness classified

Affected products

And 1 more affected product. See all after sign-in

Technical detail

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N

Scored 8.2 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity HighRequires specific conditions like a race condition or non-default configuration
  • Privileges Required LowRequires basic user-level privileges
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope ChangedThe exploit can affect other components (e.g. sandbox escape, host compromise from VM)

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability NoneNo availability impact

Weaknesses

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for GitLab, not every advisory.