Skip to main content
Mallory
CriticalVulnerability

CVE-2026-89078: Authenticated Code Execution in GitLab CI/CD Regular-Expression Parsing

Published Sep 23, 2026 · Updated 2 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days29 mentions · peak 5 in a dayToday
CVSS9.9Critical · v3.1
EPSS1.2%69th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
GitLab
IdentifiersCVE-2026-89078CWE-415 · Double Free

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

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.

VendorProductType
GitLabGitlabapplication
FAQ

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.
Activity feed

Recent activity

85 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
tenable nessus pluginsNews · Nov 20, 2026GLSA-202611-12 : Ruby: Multiple Vulnerabilities | Tenable®Listed among the Ruby vulnerabilities covered by Gentoo advisory GLSA-202611-12. Updates are provided, but the individual flaw's technical details are not described.Read more ↗tenable nessus pluginsNews · Nov 11, 2026Rocky Linux 10.2 [CIQ] Security Update: ruby / ruby-bundled-ge... | Tenable®A double-free vulnerability in Ruby's regular expression parser affecting Ruby packages on Rocky Linux 10.2. CIQ advisory crlsa-2026_96235 provides security updates. The plugin reports exploit availability and a CISA KEV deadline collectively, without identifying which listed vulnerabilities those indicators concern.Read more ↗tenable nessus pluginsNews · Nov 11, 2026Rocky Linux 9 [CIQ] Security Update: ruby / ruby-debuginfo / r... | Tenable®A double-free vulnerability in Ruby's regular expression parser affecting Ruby packages on Rocky Linux 9. Updates are available through CIQ advisory crlsa-2026_96067. The plugin reports available exploits and a CISA Known Exploited Vulnerability due date collectively, without identifying which individual CVEs those statements concern.Read more ↗tenable nessus pluginsNews · Nov 11, 2026TencentOS Server 4: ruby (TSSA-2026:1378) | Tenable®A double-free vulnerability in regular-expression parsing of GitLab CI/CD configurations could allow an authenticated user to execute arbitrary code on the GitLab server under certain conditions. Affected GitLab CE/EE versions are 19.2 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1. The TencentOS Server 4 advisory supplies ruby package updates addressing the vulnerability. The plugin reports a CVSS v3 base score of 9.9 and detects exposure using self-reported version information rather than exploitation testing.Read more ↗
+26 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity44Community discussion across Reddit, Mastodon, and other social sources.