GPU VulnDB

Database/Control plane, storage & DevOps

GitLab: user with an unconfirmed email can be granted Group Owner during group import

CVSS 3.7CVE-2026-129252Control plane, storage & DevOpscurated

Impact

Group import does not properly check email verification when it maps imported members to local accounts. An account with an unconfirmed email address can end up with Owner-level membership on the imported group. A group owner controls the group's CI/CD variables, runners and member list, so on an instance that builds fleet images or drives deployments this is a path to those credentials and pipelines. Exploitation needs high attack complexity and user interaction (someone else has to run the import). Affects all versions before 19.3.9, 19.4 before 19.4.8 and 19.5 before 19.5.6.

Who can reach it

An authenticated GitLab user with an unconfirmed email address. Another user has to perform a group import whose member mapping matches that account. Network access to the instance is required.

What to do

Upgrade to 19.3.9, 19.4.8 or 19.5.6 per the GitLab 19.5.6 patch release. This is a package upgrade and a service restart on a self-managed instance. After upgrading, check the membership of recently imported groups for owners whose email is unconfirmed.

References

Related entries

All Control plane, storage & DevOps entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.