Max-Severity GitLab RCE Affects All Versions Since 2014
Original source
Critical GitLab Flaw (CVSS 10.0) Could Allow Unauthenticated RCE Across 12 Years of Releases
The Hacker News →GitLab released critical patches on October 21 for CVE-2026-110264, a maximum-severity RCE flaw affecting every version since 7.0 (2014). An integer overflow in the Onigmo regex compiler bundled within GitLab allows unauthenticated attackers to execute arbitrary code on self-managed instances. The company provided no preconditions for exploitation, has detected no active attacks, and the vulnerability is not listed on CISA’s known exploited vulnerabilities catalog. GitLab published two detection rules (“Onigmo native worker crash” and “Org mode render error burst”) in its open-source TLDR framework but offered no interim workaround.
The vulnerability spans decades because Onigmo has shipped in GitLab’s packages since 2014. To address this range, GitLab backported patches to versions 18.11.13, 19.0.10, 19.1.9, and 19.2.9—releases normally outside the support window—alongside the three currently maintained versions. This wider reach contrasts with an October 12 patch (CVE-2026-97229), which was also a maximum-severity unauthenticated overflow but only extended back to version 19.2.
Researcher joaxcar reported four code-execution flaws in GitLab’s regex engine within a month, including two from late September (both 9.9-rated, requiring authentication). The October 21 release fixes 11 security issues total, including an account-takeover vulnerability when both SAML and LDAP authentication are enabled (CVE-2026-15723, 8.2-rated) and a cache-poisoning flaw in OAuth/OpenID Connect endpoints (CVE-2026-112212, 7.5-rated). Database changes in patched versions may require downtime on single-node deployments.
Read the full article
Continue reading at The Hacker News →This is an AI-generated summary. Read the original for the full story.