GPU VulnDB

Database/Control plane, storage & DevOps

GitLab EE: unassigned scheduled pipeline execution policy can still run code in protected pipelines

CVSS 6.2CVE-2026-85778Control plane, storage & DevOpscurated

Impact

An authenticated user can get code to run in protected pipelines through a scheduled pipeline execution policy even after that policy was unassigned, because the authorization checks are wrong. Protected pipelines are where deploy credentials, registry push tokens and cluster access usually live, so code running there can reach whatever the pipeline deploys to, including GPU clusters and model registries. GitLab says this happens only under certain conditions and needs high privileges and user interaction.

Who can reach it

Authenticated GitLab user with high privileges (PR:H) on a GitLab EE instance, over the network. User interaction is needed.

What to do

Upgrade GitLab EE to 19.3.9, 19.4.8 or 19.5.6 or later, which restarts the GitLab services. Until then, check scheduled pipeline execution policies that were recently unassigned from projects with protected pipelines. GitLab.com is patched by the vendor.

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.