Description
GitLab has remediated an issue in GitLab EE affecting all versions from 12.0 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1 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.
Affected products
gitlab: gitlab
References3
- docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-1-re… Release NotesVendor Advisory
- gitlab.com/gitlab-org/gitlab/-/work_items/606479 Permissions Required
- hackerone.com/reports/3809350 Permissions Required
Metrics
- CVSS 3.1
-
7.1
HIGH
Score source: NVD
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N - EPSS — exploit probability
- 0% percentile: 18 · as of 8 November 2026
- CWE
- CWE-863
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.