Is CVE-2026-110264 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-110264 being exploited in the wild.

How severe is CVE-2026-110264?

Critical severity, with a CVSS score of 10, published 22 October 2026.

Which products and versions are affected?

GitLab CE 7.0 to 18.11.12, 19.0.0 to 19.0.9, 19.1.0 to 19.1.8, 19.2.0 to 19.2.8, 19.3.0 to 19.3.5, 19.4.0 to 19.4.2, 19.5.0; GitLab EE 7.0 to 18.11.12, 19.0.0 to 19.0.9, 19.1.0 to 19.1.8, 19.2.0 to 19.2.8, 19.3.0 to 19.3.5, 19.4.0 to 19.4.2, 19.5.0.

Is there a fix for CVE-2026-110264?

Yes: fixed in GitLab CE/EE 18.11.13, 19.0.10, 19.1.9, 19.2.9, 19.3.6, 19.4.3, 19.5.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-110264 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-110264?

Check whether you run GitLab CE or GitLab EE at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-110264: GitLab integer overflow in regular expression compiler

CVE-2026-110264 · Severity: critical · CVSS 10 · Published 2026-10-22

GitLab is a web-based version control and collaboration platform used by development teams to manage source code and coordinate software projects. An integer overflow vulnerability in its regular expression compiler allows unauthenticated attackers to execute arbitrary code by submitting a specially crafted regex pattern. An attacker could gain full control of the GitLab server and access all data hosted on it.

Technologies: GitLab CE, GitLab EE. Vendors: GitLab.

Quick answers

Is CVE-2026-110264 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-110264 being exploited in the wild.
How severe is CVE-2026-110264?: Critical severity, with a CVSS score of 10, published 22 October 2026.
Which products and versions are affected?: GitLab CE 7.0 to 18.11.12, 19.0.0 to 19.0.9, 19.1.0 to 19.1.8, 19.2.0 to 19.2.8, 19.3.0 to 19.3.5, 19.4.0 to 19.4.2, 19.5.0; GitLab EE 7.0 to 18.11.12, 19.0.0 to 19.0.9, 19.1.0 to 19.1.8, 19.2.0 to 19.2.8, 19.3.0 to 19.3.5, 19.4.0 to 19.4.2, 19.5.0.
Is there a fix for CVE-2026-110264?: Yes: fixed in GitLab CE/EE 18.11.13, 19.0.10, 19.1.9, 19.2.9, 19.3.6, 19.4.3, 19.5.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-110264 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-110264?: Check whether you run GitLab CE or GitLab EE at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: GitLab CE/EE 18.11.13, 19.0.10, 19.1.9, 19.2.9, 19.3.6, 19.4.3, 19.5.1

Technical details

An integer overflow in GitLab's regular expression compiler can be triggered by an unauthenticated user submitting a maliciously crafted regex pattern, leading to arbitrary code execution with server-level privileges. The vulnerability affects all supported versions of GitLab CE and EE from 7.0 onwards. No authentication or user interaction is required; exploitation is possible over the network.

Affected products

GitLab GitLab CE 7.0 to 18.11.12, 19.0.0 to 19.0.9, 19.1.0 to 19.1.8, 19.2.0 to 19.2.8, 19.3.0 to 19.3.5, 19.4.0 to 19.4.2, 19.5.0
GitLab GitLab EE 7.0 to 18.11.12, 19.0.0 to 19.0.9, 19.1.0 to 19.1.8, 19.2.0 to 19.2.8, 19.3.0 to 19.3.5, 19.4.0 to 19.4.2, 19.5.0

Timeline

2026-10-22: disclosed
2026-10-21: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.