CVE-2026-89078: Double Free in GitLab
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.2 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1 that under certain conditions could have allowed an authenticated user to execute arbitrary code on the GitLab server due to a double free issue when parsing a specially crafted regular expression in a CI/CD configuration.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
GitLab CE/EEto a version that resolves this vulnerability.Fixed in 19.2.7 - Upgrade
Upgrade
GitLab CE/EEto a version that resolves this vulnerability.Fixed in 19.3.3 - Upgrade
Upgrade
GitLab CE/EEto a version that resolves this vulnerability.Fixed in 19.4.1
Event History
Frequently Asked Questions
Which GitLab deployments are affected?
GitLab CE/EE versions 19.2 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1 are affected. Deployments outside those stated version ranges are not identified as affected by the provided information.
What does an attacker need to exploit this issue?
An attacker needs an authenticated GitLab user account and must be able to supply a specially crafted regular expression in a CI/CD configuration. No user interaction is required.
What is the potential impact of successful exploitation?
Under the affected conditions, an authenticated user could execute arbitrary code on the GitLab server. The supplied severity vector indicates high confidentiality and integrity impact, with low availability impact.
What versions remediate the issue?
Upgrade GitLab CE/EE 19.2 installations to 19.2.7 or later, 19.3 installations to 19.3.3 or later, or 19.4 installations to 19.4.1 or later.