CVE-2026-89078

9.9

GitLab · GitLab

A double free vulnerability in GitLab CI/CD configuration parsing allows authenticated users to execute arbitrary code on the server.

Executive summary

A critical remote code execution vulnerability in GitLab allows authenticated users to compromise the underlying server through malicious CI/CD configurations.

Vulnerability

This flaw stems from a double free memory management error (CWE-415) triggered during the parsing of specially crafted regular expressions within CI/CD configuration files. Any authenticated user with access to create or modify CI/CD pipelines can leverage this flaw to achieve remote code execution on the server.

Business impact

The ability to execute arbitrary code on a GitLab server represents a total compromise of the CI/CD environment. This risk is severe because attackers could steal sensitive environment variables, inject malicious code into production software builds, or move laterally into the internal network. With a CVSS score of 9.9, this vulnerability is classified as critical, reflecting the high potential for unauthorized access and full system takeover.

Remediation

Immediate Action: Upgrade GitLab instances immediately to versions 19.2.7, 19.3.3, or 19.4.1 to apply the necessary memory management patches.

Proactive Monitoring: Review CI/CD pipeline configuration logs for unusual activity or rejected jobs, and monitor server memory usage for patterns indicative of repeated crashes or instability.

Compensating Controls: Restrict permissions for creating and editing CI/CD pipelines to trusted users only, and implement strict egress filtering on the GitLab server to limit the impact of potential command execution.

Exploitation status

Public Exploit Available: Yes, a published proof of concept exists, as documented in the HackerOne report linked in the CVE references.

Analyst recommendation

Given the critical nature of this vulnerability and the potential for full server compromise, organizations must prioritize patching their GitLab instances immediately. Ensure that the update is applied across all nodes in the infrastructure to eliminate the risk of arbitrary code execution. If patching is not immediately feasible, restrict access to pipeline configuration features to minimize the attack surface until the remediation is complete.

More GitLab CVEs all →

History

  1. Disclosed CVE record published
  2. Collected by CVE Brief via github
  3. Analyst report written
  4. Published in the daily brief critical section

Sources

Originally found and disclosed by Thanks [joaxcar](https://hackerone.com/joaxcar) for reporting this vulnerability through our HackerOne bug bounty progra, per the CVE Program record.