GitLab up to 19.5.0 Regular Expression Compilation integer overflow

Summaryinfo

A vulnerability marked as very critical has been reported in GitLab up to 19.5.0. This vulnerability affects unknown code of the component Regular Expression Compilation. This manipulation causes integer overflow. This vulnerability is registered as CVE-2026-110264. Remote exploitation of the attack is possible. No exploit is available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability has been found in GitLab up to 19.5.0 and classified as very critical. Affected by this vulnerability is an unknown code of the component Regular Expression Compilation. The manipulation with an unknown input leads to a integer overflow vulnerability. The CWE definition for the vulnerability is CWE-190. The product performs a calculation that can produce an integer overflow or wraparound, when the logic assumes that the resulting value will always be larger than the original value. This can introduce other weaknesses when the calculation is used for resource management or execution control. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

An issue has been discovered in GitLab CE/EE affecting all 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 that, under certain conditions, 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.

The advisory is shared at gitlab.com. This vulnerability is known as CVE-2026-110264 since 10/13/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/22/2026).

Upgrading to version 18.11.13, 19.0.10, 19.1.9, 19.2.9, 19.3.6, 19.4.3 or 19.5.1 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-107696). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Bug Tracking Software

Name

• GitLab

Version

• 18.11.0
• 18.11.1
• 18.11.2
• 18.11.3
• 18.11.4
• 18.11.5
• 18.11.6
• 18.11.7
• 18.11.8
• 18.11.9
• 18.11.10
• 18.11.11
• 18.11.12
• 19.0
• 19.0.0
• 19.0.1
• 19.0.2
• 19.0.3
• 19.0.4
• 19.0.5
• 19.0.6
• 19.0.7
• 19.0.8
• 19.0.9
• 19.1
• 19.1.0
• 19.1.1
• 19.1.2
• 19.1.3
• 19.1.4
• 19.1.5
• 19.1.6
• 19.1.7
• 19.1.8
• 19.2
• 19.2.0
• 19.2.1
• 19.2.2
• 19.2.3
• 19.2.4
• 19.2.5
• 19.2.6
• 19.2.7
• 19.2.8
• 19.3
• 19.3.0
• 19.3.1
• 19.3.2
• 19.3.3
• 19.3.4
• 19.3.5
• 19.4
• 19.4.0
• 19.4.1
• 19.4.2
• 19.5.0

License

• open-source

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion