Skip to main content
Mallory
CriticalVulnerability

CVE-2026-93577: Regular Expression Compiler Integer Overflow Leading to Code Execution in GitLab CE/EE

Published Sep 23, 2026 · Updated 1 day ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days45 mentions · peak 8 in a dayToday
CVSS9.9Critical · v3.1
EPSS0.93%62nd percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
GitLab
IdentifiersCVE-2026-93577CWE-190 · Integer Overflow or Wraparound

CVE-2026-93577 is an integer overflow vulnerability in Ruby's regular-expression compiler, associated with wrapped jump offsets in Onigmo. In GitLab Community Edition and Enterprise Edition, compilation of a specially crafted regular expression in a CI/CD configuration can allow an authenticated user to execute arbitrary code on the GitLab server under certain conditions. Affected GitLab versions are 19.2 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1. The issue also affects Ruby packages covered by operating-system security updates. The precise additional conditions required for successful code execution are not specified.

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 through GitLab can result in arbitrary code execution on the GitLab server, potentially compromising the confidentiality and integrity of accessible application data and disrupting service availability. The execution privilege level and the extent of access beyond the affected process are not specified. Advisory-wide exploit-availability claims, CVSS scores attributed to other vulnerabilities, and CISA remediation deadlines do not establish those properties for this CVE.

Mitigation

If you can’t patch tonight, do this now.

No vulnerability-specific workaround is specified. Until fixed releases are installed, restrict GitLab access to trusted users and networks, review project membership and privileges, and monitor for suspicious CI/CD configuration changes and anomalous server activity. These measures reduce exposure but do not correct the compiler flaw.

Remediation

Patch, then assume compromise.

Upgrade GitLab CE/EE to 19.2.7 or later in the 19.2 branch, 19.3.3 or later in the 19.3 branch, or 19.4.1 or later in the 19.4 branch. For independently deployed Ruby installations, install the applicable operating-system vendor's security-fixed packages. Identified updates include Debian 13 ruby3.3 version 3.3.13-0+deb13u1 or later and Red Hat Enterprise Linux 10 ruby4.0 build 4.0.9-38.el10_2 or a superseding vendor-fixed build. Gentoo recommends Ruby 3.3.14, 3.4.13, or 4.0.10 or later within the corresponding branch. Distribution backports mean that fixed package versions differ by platform.

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-93577 exploited in the wild?
As of Nov 21, 2026, Mallory has no reports of CVE-2026-93577 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-93577?
As of Nov 21, 2026, Mallory has found no public exploit for CVE-2026-93577.
Is there a patch for CVE-2026-93577?
Upgrade GitLab CE/EE to 19.2.7 or later in the 19.2 branch, 19.3.3 or later in the 19.3 branch, or 19.4.1 or later in the 19.4 branch. For independently deployed Ruby installations, install the applicable operating-system vendor's security-fixed packages.
What products are affected by CVE-2026-93577?
Gitlab.
How severe is CVE-2026-93577?
CVE-2026-93577 has a CVSS v3.1 score of 9.9 (Critical) and an EPSS score of 0.93% (62nd percentile) as of Nov 21, 2026.
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 activity36Community discussion across Reddit, Mastodon, and other social sources.