A critical GitLab vulnerability has been detected

A critical vulnerability, CVE-2026-110264, has been identified in GitLab Community Edition (CE) and Enterprise Edition (EE). This vulnerability is related to the processing of specially crafted regular expressions.

Under certain conditions, exploiting this vulnerability allows an unauthenticated remote attacker to execute arbitrary code on the GitLab server.

The vulnerability affects GitLab CE/EE. The minimum patched versions are 19.5.1, 19.4.3, 19.3.6, 19.2.9, 19.1.9, 19.0.10, and 18.11.13.
You must install the corresponding patched version or a newer version that includes the vulnerability fix.

The GitLab developers have released patches and recommend updating the software to the versions containing the vulnerability fix immediately.

What to do

1. Update GitLab immediately. Install the patched version corresponding to your software branch. The update is the primary measure to eliminate the vulnerability.
2. Restrict access to GitLab from the Internet. Close administrative access from the Internet—if public access to the service is not required, exclude its availability from untrusted networks. Administrative access should only be permitted from trusted networks and using secure communication channels.
3. Check access settings and the security of your GitLab instance. You need to review user permissions, accounts, access tokens, CI/CD jobs, and project settings for any unauthorized changes.
4. If GitLab was accessible from the Internet and was running on a vulnerable version, after installing the update, you must check event logs and the server status for signs of potential vulnerability exploitation.

If it is impossible to take the necessary measures, isolate the server and restrict access to it from the internet.

The Servercore team.