GitLab
Incorrect Authorization in GitLab
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.
First public PoC
None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.1high · scored by NVD · CWE-863
CISA KEV
Not listednot known exploited
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
GitLab GitLab
- >= 12.0, < 19.3.6
- >= 19.4, < 19.4.3
- >= 19.5, < 19.5.1
Fixed in 19.3.6, 19.4.3, 19.5.1
Mitigation
Upgrade to versions 19.3.6, 19.4.3, 19.5.1 or above.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.
Other public exploits
Exploit-DB, Metasploit and nuclei count as public PoCs. Exploit-tagged references from the CVE record and NVD are links only. None of these are analysed by us.| Source | Title | Published | Found by us |
|---|---|---|---|
| PoC Index | https://hackerone.com/reports/3809350 | unknown | 14 Nov 2026 |