GitLab shipped a critical patch release on October 21, 2026, fixing 12 security vulnerabilities across its Community and Enterprise editions. It covers versions 19.5.1, 19.4.3, 19.3.6, 19.2.9, 19.1.9, 19.0.10 and 18.11.13, detailed on the patch release page. Two identity bugs lead the advisory: CVE-2026-15723 and CVE-2026-112212. Both trusted input nobody checked.
Identity linking and cache poisoning
CVE-2026-15723 is high severity, CVSS 8.2, and affects GitLab CE and EE from 10.1 before 19.3.6, 19.4 before 19.4.3 and 19.5 before 19.5.1. The advisory states: “GitLab has remediated an issue 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.” It was reported by ‘stealthy’ through the HackerOne bug bounty program.
The auto-linking layer is the origin-check gap one layer down. Federation linked two identities on the strength of an email lookup it never sanitized. The advisory states no workaround. Because the flaw sits behind its stated condition, the implication is that disabling LDAP auto-linking alongside OmniAuth SAML reduces exposure: implied by the prerequisites the advisory names, not an officially stated mitigation. The advisory itself states no workaround.
CVE-2026-112212 is high severity, CVSS 7.5, and affects CE and EE from 18.3 before 19.3.6, 19.4 before 19.4.3 and 19.5 before 19.5.1. The advisory states: “GitLab has remediated an issue that, under certain conditions, an unauthenticated user could have poisoned a shared cache’s OAuth/OIDC discovery document to redirect certain flows to an externally controlled server, due to improper trust of user-supplied values when constructing endpoint URLs in cached discovery responses.” The vector carries UI:R, user interaction required. It was discovered internally by GitLab team member Peter Arts.
Discovery is a trust decision, and an agent that fetches its own identity map is trusting whatever answers the fetch. The advisory’s “certain conditions” point at a shared cache in front of a deployment serving its own OAuth/OIDC discovery, a shape implied by its description of cached discovery responses rather than stated as a prerequisite.
Membership lock, and the release’s headline fix
CVE-2026-16255, the third of these, is medium, CVSS 5.9, EE-only. The advisory states: “GitLab has remediated an issue that, when the instance-wide SAML or LDAP membership lock was enabled, an authenticated user could have granted or accepted project and group membership outside the identity provider’s control, due to incomplete enforcement of the membership lock on requests created before the lock was enabled.” It affects EE from 12.0 before 19.3.6, 19.4 before 19.4.3 and 19.5 before 19.5.1, reported by 3nvz through HackerOne.
The release’s headline fix is CVE-2026-110264, critical, CVSS 10.0: “GitLab has remediated an issue that, under certain conditions, could have allowed an unauthenticated user to execute arbitrary code on the GitLab server due to integer overflow when compiling a specially crafted regular expression.” It reaches back to version 7.0, and GitLab backported the fix beyond its standard lines to 18.11.13, 19.0.10, 19.1.9 and 19.2.9. Reported by joaxcar through HackerOne. GitLab’s security team shipped two named detections for it, “Onigmo native worker crash” and “Org mode render error burst.”
The remaining eight fixes are medium and low, spanning a GraphQL work item email field, internal response headers, a group milestones API bypass and an AI Gateway billing header.
Distinct incidents, one family
Neither identity bug reprises Forkast’s earlier GitLab coverage. On October 3 the desk covered the AI Gateway sandbox escape, a prompt-template flaw rated CVSS 9.9. On September 12 it covered the Commits-API exploitation, a CVSS 10 that drew active exploitation within hours. This pair belongs to the trust-through-defaults family Forkast has tracked in the eight-vendor bypass wave and the origin-check gap analysis: a new vendor, a new mechanism surface.
GitLab recommends all self-managed installations upgrade immediately. GitLab.com already runs the patched version, and Dedicated tenants on 19.3.5-internal0 and 19.4.2-internal0 or later need no action. Vulnerability details go public on GitLab’s issue tracker 90 days after the release that patched them. One upgrade note: the patch carries database migrations, so single-node installs go down during the upgrade while multi-node installs can avoid it with proper procedures.