CVE-2026-85778: 
GitLab vulnerability analysis and mitigation

Overview

CVE-2026-85778 is an incorrect authorization vulnerability in GitLab Enterprise Edition (EE) that allows an authenticated user to execute code in protected pipelines through a scheduled pipeline execution policy even after that policy has been unassigned. It affects GitLab EE versions 19.1 through 19.3.8, 19.4 through 19.4.7, and 19.5 through 19.5.5. The vulnerability was disclosed and patched on November 17, 2026. It carries a CVSS v3.1 base score of 6.2 (Medium) (GitHub Advisory, GitLab Patch Release).

Technical details

The root cause is classified as CWE-863 (Incorrect Authorization): GitLab EE fails to properly enforce authorization checks on scheduled pipeline execution policies after those policies have been unassigned from a project or group. Under certain conditions, a previously authorized user retains the ability to trigger code execution in protected pipelines via the stale scheduled policy, bypassing the intended access revocation. Exploitation requires network access, high privileges, high attack complexity, and user interaction, with a changed scope indicating impact beyond the vulnerable component. The vulnerability was originally reported via HackerOne report #3947781 (GitHub Advisory, GitLab Patch Release).

Impact

Successful exploitation allows a high-privileged authenticated attacker to execute arbitrary code within protected CI/CD pipelines, potentially accessing secrets, environment variables, and deployment credentials stored in those pipelines. The integrity impact is rated High, while confidentiality impact is Low and availability is unaffected. Because the scope is changed, the impact can extend beyond the directly vulnerable GitLab component to downstream systems and environments that the pipeline interacts with, such as production infrastructure or artifact repositories (GitHub Advisory).

Exploitability

There is no public proof-of-concept exploit and no evidence of in-the-wild exploitation at the time of disclosure. The EPSS score is approximately 0.0025 (0.25%), indicating a low near-term probability of exploitation. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. The NVD SSVC assessment notes the attack is not automatable and exploitation has not been observed (GitHub Advisory, GitLab Patch Release).

Exploitation steps

  1. Reconnaissance: Identify a GitLab EE instance running a vulnerable version (19.1–19.3.8, 19.4–19.4.7, or 19.5–19.5.5) with pipeline execution policies configured.
  2. Obtain high-privileged access: Authenticate to the GitLab instance with an account that previously had a pipeline execution policy assigned (e.g., a project maintainer or owner role).
  3. Trigger policy unassignment: Ensure or wait for the pipeline execution policy to be unassigned from the target project or group by an administrator.
  4. Exploit stale authorization: Leverage the scheduled pipeline execution policy that remains active due to the missing authorization re-check, triggering a scheduled pipeline run in the protected pipeline context.
  5. Execute code in protected pipeline: The pipeline runs with the permissions of the protected pipeline, potentially exposing secrets, CI/CD variables, and enabling lateral movement to connected infrastructure (GitHub Advisory).

Indicators of compromise

  • Logs: GitLab application logs showing pipeline executions triggered by a user whose policy assignment was recently revoked; audit log entries for scheduled pipeline runs on protected pipelines from unexpected users.
  • GitLab Audit Events: Events showing pipeline_execution_policy scheduled triggers after a policy unassignment event for the same user or group.
  • CI/CD Pipeline Activity: Unexpected or unauthorized pipeline runs in protected branches, particularly those initiated via scheduled execution policies rather than manual triggers.
  • Network: Outbound connections from CI/CD runners to unusual external endpoints following a pipeline execution that should not have been authorized.

Mitigation and workarounds

GitLab has released patched versions addressing this vulnerability: 19.3.9, 19.4.8, and 19.5.6. All GitLab EE users on affected versions (19.1–19.3.8, 19.4–19.4.7, 19.5–19.5.5) should upgrade immediately. As an interim measure, administrators should audit all pipeline execution policy assignments, manually remove any stale or unintended scheduled policies, and review CI/CD audit logs for unauthorized pipeline executions following recent policy changes (GitLab Patch Release, GitHub Advisory).

Community reactions

Security news outlets including GBHackers and CyberPress reported on the broader GitLab patch release that addressed 37 security vulnerabilities, of which CVE-2026-85778 was one. Coverage noted the significance of CI/CD pipeline security issues given their access to sensitive deployment secrets and infrastructure. No notable individual researcher commentary or significant social media discussion specific to this CVE has been observed beyond standard vulnerability aggregator postings.

Additional resources


Source: This report was generated using AI

Related GitLab vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-18241HIGH8.2
  • GitLab logoGitLab
  • cpe:2.3:a:gitlab:gitlab
NoYesNov 17, 2026
CVE-2026-97187HIGH7.6
  • GitLab logoGitLab
  • cpe:2.3:a:gitlab:gitlab
NoYesNov 17, 2026
CVE-2026-85778MEDIUM6.2
  • GitLab logoGitLab
  • cpe:2.3:a:gitlab:gitlab
NoYesNov 17, 2026
CVE-2026-16609MEDIUM5.4
  • GitLab logoGitLab
  • cpe:2.3:a:gitlab:gitlab
NoYesNov 17, 2026
CVE-2026-18491MEDIUM4.9
  • GitLab logoGitLab
  • cpe:2.3:a:gitlab:gitlab
NoYesNov 17, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Additional Wiz resources

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management