GPU VulnDB

Database/Control plane, storage & DevOps

GitLab EE: insufficient access control lets a limited user modify project CI/CD deployment rollback settings

CVSS 2.7CVE-2026-9268Control plane, storage & DevOpscurated

Impact

Insufficient access control checks allow an authenticated user with limited permissions to change a project's CI/CD deployment rollback settings. Where GitLab EE drives deployments onto a fleet, rollback configuration decides what can be re-deployed and under what conditions, so an unauthorized change is a change to deployment behaviour rather than to code. Integrity impact only, and the affected setting is narrow - this is a permissions-boundary bug, not a route to code execution on runners. The affected range is long, from 13.6 onward.

Who can reach it

Authenticated GitLab EE user with project permissions below those intended for the setting, over the network. The record rates privileges required as high.

What to do

Upgrade self-hosted GitLab EE to 19.2.8, 19.3.5 or 19.4.2 and restart the application - the same patch release that covers the other GitLab issues in this batch. Afterwards, review deployment rollback settings on projects with broad membership for changes made before the upgrade.

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.