Vulnerability record · CVE-2026-16255 · published 22 October 2026
CVE-2026-16255: Gitlab incorrect authorization vulnerability
Gitlab · 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.
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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
Affected products
1 vulnerable configurations from NVD's CPE data, grouped by vendor and product.
References
| Link | Tags |
|---|---|
| https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-1-released/ | Release NotesVendor Advisory |
| https://gitlab.com/gitlab-org/gitlab/-/work_items/606479 | Permissions Required |
| https://hackerone.com/reports/3809350 | Permissions Required |
Track CVE-2026-16255 inside VULONE
Watch it alongside the ransomware crews, C2 infrastructure and forum chatter that reference it, query it through the API and pull it into your SIEM over TAXII.
Related vulnerabilities
Same products first, then exploited flaws of the same weakness class.
Source: NIST National Vulnerability Database (record CVE-2026-16255), CISA KEV, FIRST EPSS (scores of 2026-11-11). This page is refreshed as NVD updates the record.