GitLab is a widely used DevOps platform; an RCE in CI can compromise repos, pipelines, runners and many organizations.
CVE-2026-89078
Authenticated RCE in GitLab CI via crafted regex (double-free).
Is CVE-2026-89078 being exploited?
Not confirmed. CVE-2026-89078 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.
How severe is CVE-2026-89078?
CVE-2026-89078 is rated Critical with a CVSS score of 9.9. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-89078?
Yes. A fix has been recorded for CVE-2026-89078. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-89078 affect?
CVE-2026-89078 affects GitLab CE/EE 19.2 before 19.2.7, GitLab CE/EE 19.3 before 19.3.3, GitLab CE/EE 19.4 before 19.4.1, Self-hosted GitLab instances running affected versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-89078?
Apply vendor patches immediately; audit CI configs, tokens, runners and logs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated user can execute arbitrary code on GitLab server via a specially crafted CI regex double-free, risking full server compromise and pipeline/artifact theft.
Immediate action required
- affected>= 19.2 and < 19.2.7
- affected>= 19.3 and < 19.3.3
- affected>= 19.4 and < 19.4.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.