CVE-2026-89078: Authenticated Code Execution in GitLab CI/CD Regular-Expression Parsing
- Vendor
- GitLab
CVE-2026-89078 is a double-free vulnerability affecting GitLab Community Edition and Enterprise Edition versions 19.2 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1. The underlying flaw is in Ruby's Onigmo regular-expression parser and occurs when pattern parsing fails after an alternation. An authenticated user who causes GitLab to parse a specially crafted regular expression in a CI/CD configuration can, under certain conditions, execute arbitrary code on the GitLab server. The flaw is triggered during regular-expression compilation, before matching occurs.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation can execute attacker-controlled code with the privileges of the affected Ruby process, potentially exposing application databases, environment secrets, and accessible filesystem data, and allowing unauthorized modification of application resources. Failed exploitation can crash the affected process and disrupt service. Root-level execution is not established.
Mitigation
If you can’t patch tonight, do this now.
Until patched, restrict GitLab access to trusted users and networks and tightly control who can submit or modify CI/CD configurations. Where application changes are possible, stop compiling attacker-controlled regular expressions; use literal string comparisons or escape user text with Regexp.escape when pattern syntax is unnecessary. Regexp.timeout does not protect against this compilation-time flaw, and pattern-length limits are not reliable protection. Monitor for unexpected Ruby worker crashes and suspicious CI/CD configuration changes.
Remediation
Patch, then assume compromise.
Upgrade GitLab CE/EE to 19.2.7, 19.3.3, or 19.4.1 for the corresponding release branch, or a later fixed release. For separately managed Ruby installations that compile untrusted patterns, deploy vendor security-fixed packages; Ruby 3.3.13 and 3.4.12 include the fix, and the double-free correction was already included in Ruby 4.0.0. Ensure the corrected runtime is actually deployed in containers and bundled application installations. Debian 13 users can install ruby3.3 version 3.3.13-0+deb13u1 or later.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2026-89078 exploited in the wild?
- As of Nov 20, 2026, Mallory has no reports of CVE-2026-89078 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-89078?
- As of Nov 20, 2026, Mallory has found no public exploit for CVE-2026-89078.
- Is there a patch for CVE-2026-89078?
- Upgrade GitLab CE/EE to 19.2.7, 19.3.3, or 19.4.1 for the corresponding release branch, or a later fixed release. For separately managed Ruby installations that compile untrusted patterns, deploy vendor security-fixed packages; Ruby 3.3.13 and 3.4.12 include the fix, and the double-free correction was already included in Ruby 4.0.0.
- What products are affected by CVE-2026-89078?
- Gitlab.
- How severe is CVE-2026-89078?
- CVE-2026-89078 has a CVSS v3.1 score of 9.9 (Critical) and an EPSS score of 1.2% (69th percentile) as of Nov 20, 2026.
Recent activity
85 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.