Database/Control plane, storage & DevOps
GitLab EE: missing authorization lets a low-privileged member change restricted project settings
Impact
A project update endpoint skips the authorization check for settings reserved to higher-privileged roles, so under certain conditions an authenticated user with a lesser role can change them. For a GPU fleet whose GitLab instance is the CI/CD and GitOps source of truth, project settings are the guardrails: protected branches, approval requirements, runner and job token scope. Loosening them is the step before pushing a build that runs on privileged GPU runners or ships an image the cluster pulls. The record rates integrity high with no confidentiality loss.
Who can reach it
Any authenticated GitLab user who already holds a lower-privileged role on the target project. Network access to the GitLab web/API endpoint; no user interaction.
What to do
Upgrade to GitLab EE 19.1.4 or 19.2.2 (or later) and restart the service — a normal GitLab patch upgrade, no fleet-wide impact. Self-managed operators should follow the linked patch release notes; GitLab.com is already patched. Afterwards, review project settings and audit events on projects with low-privileged members for changes made before the upgrade.
References
Related entries
- Grafana: alert rule marked as a server-side expression bypasses datasource query authorizationCVE-2026-17183 · Grafana (alert rule server-side expression datasource authorization)High
- GitLab: unauthenticated GraphQL mutations executed via GET through multiplex query handlingCVE-2026-19650 · GitLab CE/EE (GraphQL multiplex query handling)High
- MinIO (server-side encryption / replication): An authenticated tenant can inject SSE metadata through replicationCVE-2026-34204 · MinIO (server-side encryption / replication)High
- MinIO (S3 Select): A crafted S3 Select CSV query makes MinIO allocate memory without bound until the process isCVE-2026-39414 · MinIO (S3 Select)High
- RabbitMQ: super-stream binding-keys parsed before the permission check, one PUT kills the nodeCVE-2026-67408 · RabbitMQ (rabbitmq_stream_management super-stream binding-keys handler)High
- Jenkins Ivy Report Plugin: XXE in Ivy report parsing gives an authenticated user file read on the controllerCVE-2026-70448 · Jenkins Ivy Report Plugin (XML parser for Ivy report files)High
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.