CVE-2026-85778 in GitLabinfo

Summary

by MITRE • 11/17/2026

GitLab has remediated an issue in GitLab EE affecting all versions from 19.1 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 that under certain conditions could have allowed an authenticated user to run code in protected pipelines through a scheduled pipeline execution policy after the policy had been unassigned due to incorrect authorization checks.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Analysis

by VulDB Data Team • 11/17/2026

GitLab Enterprise Edition versions spanning from release 19.1 up to, but not including, version 19.3.9, as well as subsequent minor releases in the 19.4 and 19.5 series prior to their respective patch levels of 19.4.8 and 19.5.6, contained a critical authorization flaw within its CI/CD pipeline execution logic. This vulnerability specifically impacts environments where protected pipelines are configured with scheduled execution policies. The core issue stems from an incorrect implementation of access control checks when managing these scheduling rules. Under specific operational conditions, the system failed to properly validate whether the user attempting to modify or interact with a scheduled pipeline had the requisite permissions associated with that particular protection rule. This lapse in authorization logic creates a pathway for authenticated users who lack explicit administrative privileges over protected pipelines to bypass intended restrictions.

The technical nature of this flaw is classified as an improper access control vulnerability, aligning closely with CWE-269 which denotes Improper Privilege Management. In the context of GitLab's architecture, protected branches and their associated pipeline rules are designed to enforce strict governance over code deployment processes. These protections typically require specific roles or group memberships to trigger builds on sensitive branches such as main or master. However, due to the defect in how scheduled pipelines interact with these protection policies, an attacker who has authenticated access to a project can manipulate the scheduling configuration. By exploiting the gap where authorization checks are incorrectly applied after a policy is unassigned or modified, the user effectively neutralizes the protective barriers intended for that branch. This allows them to execute arbitrary code within the CI/CD runner environment under the guise of a scheduled job, bypassing the manual approval gates and role-based restrictions usually enforced by protected pipeline settings.

The operational impact of this vulnerability is severe, as it directly compromises the integrity of the software delivery lifecycle. An authenticated user with lower-level privileges can escalate their access to execute code in an environment that typically requires higher trust levels. This capability enables unauthorized deployment of malicious artifacts, potential exfiltration of sensitive data stored within CI/CD variables or secrets, and further lateral movement if the runner is not properly isolated from other network resources. The ability to run code without proper authorization undermines the fundamental security model of GitLab's protected branches feature, which relies on strict adherence to role-based access controls to prevent unauthorized changes in production-bound pipelines. This scenario also maps to MITRE ATT&CK technique T1059 Command and Scripting Interpreter, as it facilitates the execution of commands within a privileged CI/CD context that should be restricted to authorized personnel only.

To mitigate this risk, organizations running affected versions must immediately upgrade their GitLab instances to version 19.3.9 or later for the 19.x series, specifically ensuring they are on at least 19.4.8 if using the 19.4 branch, and 19.5.6 or later for the 19.5 branch. These updates contain the necessary patches to correct the authorization checks associated with scheduled pipeline executions against protected branches. In addition to upgrading, administrators should review their CI/CD settings to ensure that no unauthorized users have been granted access to modify scheduling policies on critical projects during the window of exposure. It is also advisable to audit recent job logs for any suspicious activity or unexpected code execution in protected pipelines prior to applying the patch. Implementing additional network-level segmentation for runners and enforcing strict variable masking can further reduce the blast radius should a similar vulnerability be discovered in future updates, ensuring that even if an attacker gains access, their ability to impact broader infrastructure remains limited.

Responsible

GitLab

Reservation

09/04/2026

Disclosure

11/17/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Want to know what is going to be exploited?

We predict KEV entries!