CVE-2026-15723High· 8.2▾ TwilightGitLab 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 …
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 45.1 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
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.
GitLab >= 10.1 < 19.3.6GitLab >= 19.4 < 19.4.3GitLab >= 19.5 < 19.5.1Upgrade to versions 19.3.6, 19.4.3, 19.5.1 or above.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-112326Low· 3.1Improper Cleanup on Thrown Exception in GitLab
CVE-2026-105777Medium· 4.3Insertion of Sensitive Information Into Sent Data in GitLab
CVE-2026-112378Medium· 4.3Use of Less Trusted Source in GitLab
CVE-2026-103515Low· 2.7Incorrect Authorization in GitLab
CVE-2026-112212High· 7.5Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') in GitLab
CVE-2026-105711Low· 3.5Use of Cache Containing Sensitive Information in GitLab