GitLab CE/EE: environment scope matching lets an authenticated user read CI/CD variables outside their scope

Impact

Improper input validation in the environment scope pattern matcher let an authenticated GitLab user obtain CI/CD variables that were meant to be restricted to another environment. On a self-managed GitLab that drives GPU fleet automation, those variables are typically the registry pull secrets, cluster kubeconfigs, cloud credentials and model-bucket keys used by deploy jobs, so a developer with access only to a staging scope can read production material. The CVSS vector is scope-changed confidentiality only - no write or availability impact is claimed. Exposure is limited to instances where protected/scoped variables are actually used to separate trust levels.

Who can reach it

Any authenticated user of the GitLab instance with enough project access to trigger or inspect a pipeline; no admin rights and no local access needed. Network-reachable over the normal GitLab web/API surface.

What to do

Upgrade GitLab to 19.1.8, 19.2.6 or 19.3.2 (all versions from 15.7 are affected). For a self-managed instance this is a standard package or Helm upgrade with a short GitLab service restart - no node drain. Because the leak is of credential material, rotate any CI/CD variables that were scoped to environments a lower-privileged user could reach.

References

Related entries

• BOSH vSphere CPI: missing certificate pinning lets an interceptor impersonate vCenter and capture admin credentialsCVE-2026-41012 · BOSH Director vSphere CPI (vCenter REST API certificate validation)High
• OpenTelemetry Operator TargetAllocator: a tenant ServiceMonitor can exfiltrate the Collector's service-account tokenCVE-2026-47701 · OpenTelemetry Operator TargetAllocator (ServiceMonitor bearerTokenFile handling)High
• Dell OpenManage Server Administrator (improper authentication): An unauthenticated remote attacker gets unauthorizedCVE-2026-56793 · Dell OpenManage Server Administrator (improper authentication)High
• Ansible AWX: notification backends allow SSRF from the control node and leak webhook credentialsCVE-2026-71366 · Ansible AWX notification backends (webhook, Mattermost, Rocket.Chat, Grafana)High
• Grafana Alloy: ServiceMonitor bearerTokenFile reads any file and ships it to an attacker scrape targetCVE-2026-75889 · Grafana Alloy (prometheus.operator.servicemonitors component)High
• GlusterFS (brick, mknod): Mknod can create device nodes that point at real devices on the storage server, so a clientCVE-2018-10923 · GlusterFS (brick, mknod)High