Read the docs
TI-2026-79058 Aliases CVE-2026-15723GHSA-92f3-3rm4-rcgv

LDAP injection in GitLab lets users take over LDAP-backed accounts

Priority LOW 38CWE-90Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
High
Impact type
—
Confidentiality · integrity · availability
High · High · None
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA.

Summary

GitLab CE/EE from 10.1 before 19.3.6, from 19.4 before 19.4.3, and from 19.5 before 19.5.1 is affected when OmniAuth SAML and LDAP auto-linking are both enabled. Improper input sanitization in the LDAP email lookup path (CWE-90) lets an authenticated user take over an existing LDAP-backed account without any interaction from the targeted user. An attacker needs a low-privilege account and network access, and the attack is complex to carry out.

Written with Claude Haiku 5.5 from the sources below · 2026-10-28

Description from the CNA

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00543 45th percentileScored 2026-11-07
Public exploit Yes 1 exploit referenceTagged by the CNA
Fix Fixed GitLab (GitLab): 19.3.6, 19.4.3, 19.5.1

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
GitLabGitLab10.1 to before 19.3.6; 19.4 to before 19.4.3; 19.5 to before 19.5.119.3.6, 19.4.3, 19.5.1Patch availableCNA
  • GitLab VendorGitLab Affected 10.1 to before 19.3.6; 19.4 to before 19.4.3; 19.5 to before 19.5.1 Fixed in 19.3.6, 19.4.3, 19.5.1 Patch available CNA

CPE configurations NVD · 6

CPEVersionsRoleVendor
cpe:2.3:a:gitlab:gitlab:*:*:*:*:community:*:*:*10.1.0 to before 19.3.6VulnerableGitLab
cpe:2.3:a:gitlab:gitlab:*:*:*:*:enterprise:*:*:*10.1.0 to before 19.3.6VulnerableGitLab
cpe:2.3:a:gitlab:gitlab:*:*:*:*:community:*:*:*19.4.0 to before 19.4.3VulnerableGitLab
cpe:2.3:a:gitlab:gitlab:*:*:*:*:enterprise:*:*:*19.4.0 to before 19.4.3VulnerableGitLab
cpe:2.3:a:gitlab:gitlab:19.5.0:*:*:*:community:*:*:*19.5.0VulnerableGitLab
cpe:2.3:a:gitlab:gitlab:19.5.0:*:*:*:enterprise:*:*:*19.5.0VulnerableGitLab
  • cpe:2.3:a:gitlab:gitlab:*:*:*:*:community:*:*:* Versions 10.1.0 to before 19.3.6 Vulnerable ·GitLab
  • cpe:2.3:a:gitlab:gitlab:*:*:*:*:enterprise:*:*:* Versions 10.1.0 to before 19.3.6 Vulnerable ·GitLab
  • cpe:2.3:a:gitlab:gitlab:*:*:*:*:community:*:*:* Versions 19.4.0 to before 19.4.3 Vulnerable ·GitLab
  • cpe:2.3:a:gitlab:gitlab:*:*:*:*:enterprise:*:*:* Versions 19.4.0 to before 19.4.3 Vulnerable ·GitLab
  • cpe:2.3:a:gitlab:gitlab:19.5.0:*:*:*:community:*:*:* Versions 19.5.0 Vulnerable ·GitLab
  • cpe:2.3:a:gitlab:gitlab:19.5.0:*:*:*:enterprise:*:*:* Versions 19.5.0 Vulnerable ·GitLab

Remediation

Upgrade GitLab to 19.3.6, 19.4.3, or 19.5.1. The vendor's fixed versions are 19.3.6, 19.4.3, and 19.5.1.

Written with Claude Haiku 5.5 from the sources below · 2026-10-28

  • Fix · CNA GitLab (GitLab) Fixed in 19.3.6, 19.4.3, 19.5.1

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    GitLab 19.3.6, 19.4.3, 19.5.1

    11 records Highest priority Priority LOW 11 LOW

    Other records, highest priority first

    • TI-2026-79063 Cache poisoning in GitLab OAuth/OIDC discovery redirects flowsPriority LOW 32
    • TI-2026-79055 Incorrect authorization in GitLab lets read_api tokens create work itemsPriority LOW 32
    • TI-2026-79059 Incorrect authorization in GitLab lets users bypass membership locksPriority LOW 31

Timeline

  1. 2026-10-21 Threatist record created from CVE-2026-15723
  2. 2026-10-22 Alias added: GHSA-92f3-3rm4-rcgv
  3. 2026-10-23 CISA SSVC decision points changed
  4. 2026-10-23 Priority changed: MEDIUM → LOW
  5. 2026-10-23 CISA SSVC decision points changed

References

  • TI-2026-71508 Integer overflow in GitLab allows code execution on the server KEVCVSS 3.1CRITICAL 10.0
  • TI-2026-58817 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in GitLab KEVCVSS 3.1CRITICAL 10.0
  • TI-2023-06425 Weak Password Recovery Mechanism for Forgotten Password in GitLab KEVCVSS 3.1CRITICAL 10.0
  • TI-2021-05191 Code injection in GitLab KEVCVSS 3.1CRITICAL 10.0
  • TI-2021-05161 Server-side request forgery in GitLab KEVCVSS 3.1CRITICAL 9.8
  • TI-2022-02763 Injection in GitLab CVSS 3.1CRITICAL 9.9
See all 1506 →

Sources