GitLab just patched its second perfect 10 in two weeks, and last week's patch does NOT fix this one. Self-hosting GitLab? Check your version now.
CVE-2026-110264 (CVSS 3.1: 10.0 Critical) is an integer overflow when GitLab compiles a specially crafted regular expression. Under certain conditions it lets an unauthenticated attacker run code on the server.
Who is affected: self-managed GitLab CE/EE, every version since 7.0. GitLab.com and GitLab Dedicated are already patched.
Fixed versions (released Oct 21, 2026):
19.5.1 | 19.4.3 | 19.3.6 | 19.2.9 | 19.1.9 | 19.0.10 | 18.11.13
Why you must update again: last week's critical, CVE-2026-97229, was another regex-related CVSS 10. Its fixed builds (19.2.8, 19.3.5, 19.4.2) still fall inside the new affected ranges.
GitLab reports no exploitation so far. It has released two detections to help spot attempts.
What to do:
1. Upgrade to your branch's fixed version
2. Limit internet exposure of the instance where you can
3. Deploy GitLab's detections
Source: https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-1-released/