GitLab patches max-severity RCE flaw reaching back 12 years
GitLab on 22 October 2026 released fixes for CVE-2026-110264, an integer-overflow bug letting unauthenticated users run arbitrary code on self-managed servers across releases dating to GitLab 7.0 from June 2014.
Photo: The RegisterKey points
GitLab patched CVE-2026-110264, a max-severity integer-overflow flaw allowing unauthenticated remote code execution on self-managed servers across releases back to GitLab 7.0.
GitLab on 22 October 2026 released security patches for a maximum-severity flaw, tracked as CVE-2026-110264, that could let unauthenticated attackers execute arbitrary code on self-managed servers under certain conditions. The integer overflow bug reaches back 12 years of releases, to GitLab 7.0 from June 2014, and carries a perfect 10 CVSS severity rating.
The flaw matters because GitLab is not merely a code repository: it holds source code, continuous integration and continuous deployment (CI/CD) pipelines, and the secrets those pipelines use to deploy to production, said Frank Dickson, principal analyst at Dickson Research. "Owning the GitLab server means owning the keys to the kingdom," he said. GitLab claims 50 million registered users and more than 50 percent of the Fortune 100.
What the flaw allows
The vulnerability is an integer overflow in GitLab's Regular Expression Compiler, a background engine that parses and validates regular expressions in configuration files. GitLab's release notes state that, under certain conditions, the bug "could have allowed an unauthenticated user to execute arbitrary code on the GitLab server due to integer overflow when compiling a specially crafted regular expression."
Impacted versions span all GitLab Community Edition (CE) and Enterprise Edition (EE) versions from 7.0 before 18.11.13, 19.0 before 19.0.10, 19.1 before 19.1.9, 19.2 before 19.2.9, 19.3 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1. GitLab 7.0 was released in June 2014, meaning the affected software releases date back a full 12 years.
GitLab released fixes in versions 19.5.1, 19.4.3, and 19.3.6, and backported the patch to versions 19.2.9, 19.1.9, 19.0.10, and 18.11.13. GitLab "strongly recommends" that all organizations running vulnerable software upgrade to a fixed version "as soon as possible." GitLab-managed infrastructure, including GitLab.com and GitLab Dedicated, remains patched, and GitLab Dedicated tenants running 19.3.5-internal0 and 19.4.2-internal0 or later already include the fixes.
Where the numbers came from
Internet threat watchdog Shadowserver now tracks over 2,700 GitLab Community Edition instances exposed online, though it does not say how many are honeypots or already secured. The flaw scored a perfect 10 CVSS severity rating. GitLab warned customers ten days earlier about another critical remote code execution vulnerability, CVE-2026-97229, with a 10/10 CVSS base score in the CI/CD Regular Expression Compiler, reported by the same researcher.
Bug hunter Johan Carlsson reported the vulnerability through GitLab's HackerOne bug bounty program, using the handle 'joaxcar'. GitLab also released two threat detections for customers with self-managed instances. One detection is named for Onigmo, Ruby's regular expression engine, and Dickson noted the fix ships as a patch to Ruby's regular expression handling, not just GitLab's own code.
Who reported and detected it
Noah Kenney, principal consultant at Digital 520, said the issue "originates in an integer overflow within the regular expression compiler, rather than functionality developed specifically by GitLab," highlighting risks from dependencies and shared software components. SOC Prime warned that server-level compromise could enable credential theft, repository manipulation, supply chain attacks, persistence, or lateral movement. There is no indication yet of in-the-wild exploitation.
Dickson advised organizations to "Plan for downtime," noting GitLab's release notes say the patch includes database migrations and single-node instances will be down while they run. Ty Coffee, principal at UHY, said the separate LDAP account-takeover flaw risks pointing post-breach investigations at an innocent employee, and urged checking shadow and legacy GitLab servers, since older versions mean forgotten boxes are in scope.
This is the fourth critical GitLab security issue within two months, following an earlier October regex flaw and September's CVE-2026-85706, rated a perfect 10, which lets unauthenticated attackers read sensitive data. The U.S. Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2026-85706 to its list of actively exploited flaws one day later, ordering federal agencies to fix it within three days.
Since November 2021, CISA has flagged five GitLab flaws used in the wild, including one exploited in ransomware attacks. Last month, attackers began hitting another max-severity flaw in the same GitLab CE and EE products just days after the patch, according to CISA and private researchers. No in-the-wild exploitation of CVE-2026-110264 has been reported yet, but scanning of vulnerable instances is expected.
Organizations running self-managed GitLab should upgrade to versions 19.5.1, 19.4.3, 19.3.6, 19.2.9, 19.1.9, 19.0.10, or 18.11.13, and apply GitLab's two threat detections. Dickson said CISOs should ask other vendors whether their Ruby applications carry the same bug, since the flaw sits in Ruby's regex engine rather than GitLab's own code alone.
Frequently asked questions
What is CVE-2026-110264 in GitLab?
CVE-2026-110264 is an integer overflow in GitLab's Regular Expression Compiler that, under certain conditions, could let an unauthenticated user execute arbitrary code on the server by compiling a specially crafted regular expression. It scores a perfect 10 CVSS severity.
Which GitLab versions are affected and patched?
Affected versions run from GitLab 7.0 (June 2014) through 19.5. Fixes shipped in 19.5.1, 19.4.3, and 19.3.6, with backports to 19.2.9, 19.1.9, 19.0.10, and 18.11.13. GitLab.com and GitLab Dedicated are already patched.
How many GitLab instances are exposed online?
Shadowserver tracks over 2,700 internet-exposed GitLab Community Edition instances, though it does not identify how many are honeypots or already secured against attacks.


