GPU VulnDB

Database/Control plane, storage & DevOps

GitLab: Developer role can run CI/CD pipelines on protected branches via downstream pipeline creation

CVSS 8.5CVE-2026-16301Control plane, storage & DevOpscurated

Impact

Improper authorization in the downstream pipeline creation service lets an authenticated user with only the Developer role trigger CI/CD pipelines on protected branches. Protected branches are the control that decides which code can reach production runners and which jobs can use protected CI variables and deploy credentials, so this is a path from ordinary repository write access to running jobs in the trusted context. For a datacenter that drives fleet automation, image builds or node provisioning from GitLab CI, that trusted context is the one holding registry push rights and cluster credentials. CVSS scope is marked changed, reflecting the crossing of that boundary.

Who can reach it

An authenticated GitLab user holding the Developer role on an affected project. No user interaction needed.

What to do

Upgrade GitLab CE/EE to 19.2.8, 19.3.5 or 19.4.2. Versions from 18.7 are affected. This is a GitLab application upgrade and service restart, not a node-level change; self-managed operators should also review protected-branch pipeline runs and any protected-variable usage from the exposure window, since the advisory does not indicate the flaw leaves distinctive traces.

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.