GitLab Took 12 Years to Notice a Perfect 10
CVE-2026-110264 is a maximum-severity, unauthenticated code execution hole that has lived in self-managed GitLab since 2014. GitLab patched it Wednesday, Oct. 21, with no workaround and no attack path, so admins are patching blind into their own infrastructure.

A perfect CVSS score sat quietly inside GitLab's code for twelve years, and the only thing GitLab can tell self-hosted customers now is to patch immediately and hope.
The verdict: this is a maximum-severity, unauthenticated remote-code-execution bug that has been open since before most of your engineers were hired.
On Wednesday, Oct. 21, GitLab shipped emergency fixes for CVE-2026-110264, an integer overflow in Onigmo, the regular-expression engine Ruby bundles. The flaw is a 10/10 CVSS score—no privileges, no clicks, no login—and it reaches back to GitLab 7.0, released in 2014.
Fixed releases landed across seven branches at once: 19.5.1, 19.4.3, 19.3.6, 19.2.9, 19.1.9, 19.0.10, 18.11.13 for both Community Edition and Enterprise Edition. GitLab normally patches only the three newest minor releases; breaking its own policy to backport this four branches deeper signals how it graded the risk internally.
Patching Blind, On Purpose
GitLab-managed infrastructure, including GitLab.com and GitLab Dedicated, was patched. Self-managed customers did not get that head start. GitLab has not disclosed which feature triggers the overflow. One detection rule points at rendering Org mode files, but GitLab has not confirmed it. There is no workaround: you cannot harden your instance, firewall the specific feature, or check your logs with confidence for something you cannot name.
Translation: GitLab's two new Sigma detection rules are the only lantern in the room. GitLab reports no sign the flaw has been exploited and it is not listed in the U.S. CISA catalog of known exploited vulnerabilities as of Thursday, Oct. 22. That's reassuring until you remember absence of alarm bells isn't the same as absence of a break-in.
Full technical detail won't surface until GitLab makes the issue reports public 90 days after the fix, expected in January 2027.

This Is Not a One-Off
This is the second maximum-severity regex-engine RCE GitLab has shipped in under two weeks. GitLab fixed CVE-2026-97229 on Sunday, Oct. 12. CVE-2026-110264 is a separate flaw with wider reach; a server on 19.4.2, 19.3.5 or 19.2.8 remains exposed.
Same researcher both times. One person working through GitLab's bug bounty found four code-execution flaws in GitLab's regular-expression engine in thirty days. That is not bad luck. That is a part of the codebase nobody had stress-tested properly in over a decade, and it just got found by someone who decided to look.
The stakes are concrete. GitLab says over 30 million registered users and more than 50% of Fortune 100 companies use its platform, including Nvidia, T-Mobile, Lockheed Martin, Airbus, and Goldman Sachs. A self-managed GitLab box is source code, CI/CD secrets, and deploy keys in one place. For twelve years an unauthenticated attacker could have walked in the front door.
GitLab also quietly patched a high-severity bug that lets an attacker take over an existing LDAP-backed account without any user interaction, due to improper input sanitization in the LDAP email lookup path. Nobody's talking about that one today, because the 10.0 is eating all the oxygen in the room, which is exactly how a company would prefer it.
What to watch: whether GitLab's January 2027 disclosure confirms the Org-mode rendering path, whether any breach notifications surface from self-managed customers who patched late, and whether joaxcar finds a fifth hole in this engine before year's end.
- GitLab Critical Patch Release: 19.5.1, 19.4.3, 19.3.6, 19.2.9, 19.1.9, 19.0.10, 18.11.13
- Critical GitLab Flaw (CVSS 10.0) Could Allow Unauthenticated RCE Across 12 Years of Releases
- GitLab CVE-2026-110264 RCE: Fixed Versions
- CVE-2026-110264: GitLab Integer Overflow (CVSS 10)
- 12-Year-Old GitLab Vulnerability Allows Remote Code Execution on Self-Managed Server
- Critical GitLab Flaw (CVSS 10.0) Could Allow Unauthenticated RCE Across 12 Years of Releases
- GitLab warns of max severity code execution vulnerability
- GitLab Patches CVSS 10.0 Unauthenticated RCE Affecting Releases Back to Version 7.0
- GitLab Critical Patch Release Fixes 10.0 CVSS Remote Code Execution Flaw and 11 Other Bugs
- GitLab servers taken over with no login through a crafted Org-mode file, even after the Oct 12 patch (CVE-2026-110264)
- CVE-2026-110264: Η GitLab διορθώνει κρίσιμη ευπάθεια
- Aikido on X: "Another one 🚨 Gitlab is vulnerable to remote code execution. 1. Firewall your Gitlab server 2. Patch. CVE-2026-110264 is a CVSS 10.0 unauthenticated RCE in GitLab’s regex compiler. It reaches self-managed CE/EE instances back to version 7.0, while @gitlab.com is already patched.… / X
- Pirat_Nation 🔴 on X: "GitLab has patched a critical security flaw with a CVSS score of 10.0, the highest possible severity. The vulnerability, CVE-2026-110264, could allow an unauthenticated attacker to execute arbitrary code on self-managed GitLab servers. It affects GitLab versions dating back… / X
- GitLab has released security patches for 12 vulnerabilities, including one of the most critical vulnerabilities that could allow arbitrary code execution. - GIGAZINE
- GitLab Patch Releases
- Critical Vulnerability in GitLab Community Edition and Enterprise Edition
- Critical GitLab GraphQL Flaw Could Let Unauthenticated Attackers Delete Public Projects
- GitLab release and maintenance policy
- GitLab's AI Strategy: How the All-Remote DevSecOps Leader Listens to Millions of Users in 2026
- GitLab vs GitHub: In-Depth Comparison & Platform Choice Guide
- GitHub vs GitLab: 1 Key Difference in 2026 [Tested]
- Git Market Share Statistics 2026: Developer Adoption And Usage Trends
- GitLab Data Security Insights & Best Practices
- GitLab CVE-2026-85706: Critical CVSS 10.0 Path Traversal Flaw
- GitLab warns of critical RCE vulnerability in AI Gateway service
- GitLab Premium Self-Managed - AWS Marketplace