Incorrect Authorization in GitLab
2 public exploits exists; no exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in GitLab 19.3.6, GitLab 19.4.3 and GitLab 19.5.1.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| GitLab | GitLab | >=12.0.0 <19.3.6, >=19.4.0 <19.4.3, =19.5.0, >=12.0 <19.3.6, >=19.4 <19.4.3, >=19.5 <19.5.1 | 19.3.6, 19.4.3, 19.5.1 |
Exploit evidence
2 public sources
Vendor advisories
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in GitLab, strongest first
Embed
A live severity badge for an advisory, README or ticket