Is CVE-2026-15723 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-15723 being exploited in the wild.

How severe is CVE-2026-15723?

High severity, with a CVSS score of 8.2, published 22 October 2026.

Which products and versions are affected?

GitLab Community Edition 10.1 before 19.3.6, 19.4 before 19.4.3, 19.5 before 19.5.1; GitLab Enterprise Edition 10.1 before 19.3.6, 19.4 before 19.4.3, 19.5 before 19.5.1.

Is there a fix for CVE-2026-15723?

Yes: fixed in 19.3.6, 19.4.3, 19.5.1, 19.2.9, 19.1.9, 19.0.10, 18.11.13. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-15723 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-15723?

Check whether you run GitLab Community Edition or GitLab Enterprise Edition at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-15723: GitLab authentication bypass in OmniAuth SAML/LDAP auto-linking

CVE-2026-15723 · Severity: high · CVSS 8.2 · Published 2026-10-22

GitLab is a web-based platform for managing source code repositories and CI/CD pipelines. When both OmniAuth SAML and LDAP auto-linking are enabled, an authenticated attacker can hijack existing LDAP-backed accounts without the target user's knowledge or interaction. This could lead to unauthorized access to code repositories and sensitive project data.

Technologies: GitLab Community Edition, GitLab Enterprise Edition. Vendors: GitLab.

Quick answers

Is CVE-2026-15723 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-15723 being exploited in the wild.
How severe is CVE-2026-15723?: High severity, with a CVSS score of 8.2, published 22 October 2026.
Which products and versions are affected?: GitLab Community Edition 10.1 before 19.3.6, 19.4 before 19.4.3, 19.5 before 19.5.1; GitLab Enterprise Edition 10.1 before 19.3.6, 19.4 before 19.4.3, 19.5 before 19.5.1.
Is there a fix for CVE-2026-15723?: Yes: fixed in 19.3.6, 19.4.3, 19.5.1, 19.2.9, 19.1.9, 19.0.10, 18.11.13. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-15723 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-15723?: Check whether you run GitLab Community Edition or GitLab Enterprise Edition at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: 19.3.6, 19.4.3, 19.5.1, 19.2.9, 19.1.9, 19.0.10, 18.11.13

Technical details

An improper input sanitization vulnerability in the LDAP email lookup path during OmniAuth identity linking allows an authenticated user to take over LDAP-backed accounts. The vulnerability requires both OmniAuth SAML and LDAP auto-linking to be enabled, and the attacker must be an authenticated user. The flaw permits account hijacking without any user interaction from the victim.

Affected products

GitLab Community Edition 10.1 before 19.3.6, 19.4 before 19.4.3, 19.5 before 19.5.1
GitLab Enterprise Edition 10.1 before 19.3.6, 19.4 before 19.4.3, 19.5 before 19.5.1

Timeline

2026-10-22: disclosed
2026-10-21: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.