GPU VulnDB

Database/Control plane, storage & DevOps

GitLab CE/EE: missing enforcement checks let an authenticated user bypass SAML SSO restrictions

CVSS 5.4CVE-2026-12910Control plane, storage & DevOpscurated

Impact

Missing authentication enforcement checks allowed an authenticated user, under conditions GitLab does not detail, to sign in without going through SAML SSO. Where SSO is the control that ties repository and pipeline access to the identity provider - including offboarding, MFA and conditional access - a bypass means those gates can be sidestepped for the source and CI system that builds what runs on the fleet. Rated low for both confidentiality and integrity, so this is a control weakening rather than direct data theft. Affects 18.6 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2. Distinct from CVE-2026-82837 in the same release: different flaw, different affected range.

Who can reach it

An authenticated GitLab user reaching the instance over the network; low privileges required, no user interaction.

What to do

Upgrade self-managed GitLab to 19.1.8, 19.2.6 or 19.3.2 - a package upgrade and service restart on the GitLab instance. Review sign-in audit events for group members who authenticated without SSO in the affected window. GitLab.com is already patched.

References

Related entries

All Control plane, storage & DevOps entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.