GitLab CE/EE CI/CD Regular Expression Remote Code Execution Vulnerabilities
Release Date: 21st September 2026
Impact : CRITICAL
TLP Rating: Clear 
The Department of Communications and Digital Transformation (DCDT) through CERT Vanuatu (CERTVU), provides the following advisory.
This alert is relevant to Organizations and System/Network administrators that utilize the above product(s). This alert is intended to be understood by technical users and systems administrators.
What is it?
CVE-2026-89078 and CVE-2026-93577 are two critical memory safety vulnerabilities in GitLab Community Edition (CE) and Enterprise Edition (EE), each rated CVSS 9.9. CVE-2026-89078 is a double free when parsing a specially crafted regular expression in a CI/CD configuration. CVE-2026-93577 is an integer overflow when compiling a specially crafted regular expression in a CI/CD configuration. In both cases an authenticated user who can supply a CI/CD configuration could execute arbitrary code on the GitLab server. Both were reported through HackerOne and fixed in the same patch release on 23 September 2026, so CERTVU has combined them in this advisory.
The patch release also fixes nine other flaws, including a cross-site scripting issue in the merge request diff viewer (CVE-2026-84739, CVSS 8.7) and a missing authorization issue in the GitLab Duo job troubleshooting feature (CVE-2026-92470, CVSS 7.7).
What are the systems affected?
The following GitLab CE/EE versions are affected:
GitLab 19.2 before 19.2.7
GitLab 19.3 before 19.3.3
GitLab 19.4 before 19.4.1
Self-managed instances must be updated by the customer.
Not affected / patched version:
GitLab 19.2.7, 19.3.3, 19.4.1 or later. GitLab.com is already patched and GitLab Dedicated customers need no action.
What does this mean?
Successful exploitation may allow attackers to:
Run arbitrary code on the GitLab server by submitting a crafted CI/CD configuration, once logged in
Steal source code, CI/CD variables, tokens and deploy keys held by the server, and tamper with code and pipelines
Use the compromised server to attack the build, test and production systems that it connects to
Mitigation process?
CERTVU recommends the following:
-
Upgrade immediately
Upgrade self-managed GitLab to 19.4.1, 19.3.3 or 19.2.7 or later. GitLab lists no workaround. Single-node instances will have downtime during the upgrade, and multi-node instances can use zero-downtime upgrades. -
Reduce who can submit CI/CD configurations
Until patched, disable open sign-up, require administrator approval for new accounts, and review users who can create projects or edit pipelines. -
Restrict network exposure
-
Review for signs of abuse
-
Rotate secrets after a suspected compromise
If compromise is suspected, rotate CI/CD variables, access tokens, deploy keys and runner registration tokens, and report the incident to CERTVU.
Reference
- https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-4-1-released/
- https://ccb.belgium.be/advisories/warning-critical-remote-code-execution-vulnerabilities-gitlab-patch-immediately
- https://nvd.nist.gov/vuln/detail/CVE-2026-89078
- https://nvd.nist.gov/vuln/detail/CVE-2026-93577
- Download advisory (English): GitLab CE/EE CI/CD Regular Expression Remote Code Execution Vulnerabilities