GPU VulnDB

Database/Control plane, storage & DevOps

GitLab: race in pipeline job authorization exposes protected CI/CD variables

CVSS 8.2CVE-2026-18241Control plane, storage & DevOpscurated

Impact

An authenticated GitLab user can win a race condition in pipeline job authorization and get access to protected CI/CD variables and resources. Protected variables usually hold deploy credentials, registry tokens and cloud or cluster keys. On a GPU fleet those are often what pushes images and manifests to the clusters. A low-privileged project member could end up with credentials meant only for protected branches.

Who can reach it

Remote, authenticated GitLab user with access to a project. Exploiting it requires winning a race (high attack complexity).

What to do

Upgrade self-managed GitLab to 19.3.9, 19.4.8 or 19.5.6 or later. This is a GitLab service upgrade and restart, not a node reboot. Affected versions go back to 9.3. Consider rotating protected CI/CD variables if untrusted users had project access.

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.