EUVD-2025-210720
GHSA-j94w-j9cr-q9pj
Severity by source
AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:N
The exploiting party is the pending member (low privilege); AC:H captures the three-condition prerequisite; no availability impact or scope change applies.
Primary rating from Vendor (GitLab).
CVSS VectorVendor: GitLab
Lifecycle Timeline
3DescriptionCVE.org
GitLab has remediated an issue in GitLab EE affecting all versions from 15.6 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2 that under certain conditions could have allowed a user with a pending membership to receive permissions granted by a custom role, due to incorrect privilege assignment that did not account for membership state.
AnalysisAI
Incorrect privilege assignment in GitLab Enterprise Edition allows a user with pending group membership to receive permissions granted by a custom role, bypassing the membership approval gate entirely. The flaw spans all GitLab EE versions from 15.6 through 19.2.1 - a window of approximately four years - and is documented via a public HackerOne report, though no active exploitation has been recorded in the CISA KEV catalog. The vendor-assigned CVSS score of 3.3 accurately reflects the narrow exploitation conditions: high attack complexity and high privilege prerequisites constrain real-world impact to partial confidentiality and integrity effects within a single affected group.
Technical ContextAI
GitLab Enterprise Edition's custom roles feature extends beyond the platform's built-in permission tiers, enabling administrators to define granular capability sets and assign them to group members for fine-grained RBAC. The root cause is classified as CWE-266 (Incorrect Privilege Assignment): the permission-evaluation logic that applies custom role entitlements did not validate whether a target membership was in 'active' versus 'pending' state, allowing the role's permissions to be granted before membership approval completed. The affected product is identified by CPE cpe:2.3:a:gitlab:gitlab:*:*:*:*:*:*:*:*, scoped exclusively to GitLab EE - the custom roles feature is absent from the Community Edition, so CE deployments are entirely unaffected by this code path.
RemediationAI
Upgrade GitLab EE to version 19.0.6, 19.1.4, or 19.2.2, which contain the vendor-released fix per the patch advisory at https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-2-2-released/. For operators unable to patch immediately, a targeted interim control is to audit all group memberships and defer custom role assignments until memberships transition from pending to active status; applying custom roles only to fully approved members eliminates the vulnerable code path with no functional trade-off for users who are already active. A more conservative workaround is to temporarily suspend use of custom roles entirely in groups that have pending invitations outstanding, accepting reduced RBAC granularity until patching is complete. The HackerOne report at https://hackerone.com/reports/3262844 and the GitLab issue tracker at https://gitlab.com/gitlab-org/gitlab/-/issues/565412 provide additional technical context for verification.
An issue has been discovered in GitLab CE/EE affecting all versions starting from 11.9. Rated critical severity (CVSS 10
An issue has been discovered in GitLab CE/EE affecting all versions from 16.1 prior to 16.1.6, 16.2 prior to 16.2.9, 16.
The SSH key upload feature (lib/gitlab_keys.rb) in gitlab-shell before 1.7.3, as used in GitLab 5.0 before 5.4.1 and 6.x
A vulnerability in GitLab CE/EE affecting all versions from 11.10 prior to 15.1.6, 15.2 to 15.2.4, 15.3 to 15.3.2 allows
The Kubernetes integration in GitLab Enterprise Edition 11.x before 11.2.8, 11.3.x before 11.3.9, and 11.4.x before 11.4
The Ruby SAML library is for implementing the client side of a SAML authorization. Rated critical severity (CVSS 9.8), t
A hardcoded password was set for accounts registered using an OmniAuth provider (e.g. Rated critical severity (CVSS 9.8)
An issue has been discovered in GitLab CE/EE affecting all versions starting from 12.10 before 14.6.5, all versions star
When requests to the internal network for webhooks are enabled, a server-side request forgery vulnerability in GitLab af
An issue has been discovered in GitLab CE/EE affecting all versions starting from 13.7.9 before 13.8.7, all versions sta
An issue was discovered in GitLab Omnibus 7.4 through 12.2.1. Rated critical severity (CVSS 9.8), this vulnerability is
An issue was discovered in GitLab Community and Enterprise Edition 9.x, 10.x, and 11.x before 11.5.8, 11.6.x before 11.6
Same weakness CWE-266 – Incorrect Privilege Assignment
View allSame technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today