Skip to content
VulniPulse
Sign in
Advisory severityHigh8.2GitLab Updated

High [CVE-2026-15723] 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

This high-severity GitLab advisory covers CVE-2026-15723 affecting GitLab.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-15723 Source published Source updated

VulniPulse record published Record updated

CVE-2026-15723
Affected products & platforms
GitLabUnclassified
Open source advisory

Android app · Google Play

Monitor future GitLab CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery
Get CVE alertsSee app features

Summary

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.

Affected versions
  • before 19.3.6
  • before 19.4.3
  • before 19.5.1

Official advisory · high-confidence parse· fetched 6 hours ago·verify at source

Fixed versions
  • 19.3.6
  • 19.4.3
  • 19.5.1

Official advisory · high-confidence parse· fetched 6 hours ago·verify at source

Mitigation

Upgrade to a fixed release: 19.3.6, 19.4.3, 19.5.1. That is the remediation for this advisory.

The vendor advisory may list additional interim mitigations or workarounds not captured here — review it before change work.

Official advisory · high-confidence parse· fetched 6 hours ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.