---
title: 'GitLab CVE-2026-110264: a critical vulnerability and how to fix it'
description: 'A critical vulnerability, CVE-2026-110264, with a severity score of 10 out of 10, has been discovered in GitLab, allowing code to be executed on the server without authentication. Learn how to check your GitLab version, create a backup, and safely update your server.'
image: 'https://cdn.zomro.com/uploads/blog/a48%40server-panel.net/2026/10/28/gemini_generated_image_28qo9j28qo9j28qo_q50.jpg'
---

![opened image]()

  * [Zomro](https://zomro.com/)
  * [FAQ](https://zomro.com/blog/faq/)
  * GitLab: a 10 out of 10 vulnerability that lived for 12 years. How to protect your server 



# GitLab: a 10 out of 10 vulnerability that lived for 12 years. How to protect your server

28-10-2026

![](https://cdn.zomro.com/uploads/blog/a48%40server-panel.net/2026/10/28/gemini_generated_image_28qo9j28qo9j28qo_q50.jpg)

If you have your own GitLab installed on your server, update it today. On October 21, GitLab fixed the vulnerability CVE-2026-110264 with a maximum severity score of 10 out of 10. It allows code to be executed on the server without a login or password.

The bug is present in all versions starting from 7.0. That is 12 years of releases. And even if you updated at the beginning of October, that is not enough.

> There is no workaround. The only protection is updating. Below are simple instructions.

ZOMRO / contact form

Need help from a system administrator? 

Describe the issue and we will get back to you within 15 minutes.

Your name 

Your email 

Phone 

Describe the problem 

LEAVE A REQUEST →  [ ![](/static/site/imagesNew/svg/telegram-btn-icon.svg?v=1794915141) Message us on Telegram ](https://t.me/zomro_sysadmin)

You can find the full list of services and prices on the page [ Server administration and maintenance services. ](/paid-support-services/server-management-services)

## What is GitLab

GitLab is a workspace for a team of developers. It stores code, tasks, discussions, automated builds, and deployment of a website to a server.

Imagine a safe that holds the blueprints of your entire business. Whoever gains access to GitLab can see all the code and the server passwords in the build settings, and can replace the website's code.

GitLab comes in two types:

  * **GitLab.com.** A cloud service. GitLab has already updated it itself, so you don't need to do anything.
  * **Your own GitLab on a server (self-managed).** It is installed on a VPS or a dedicated server so that the code is stored on your own infrastructure. **You are responsible for updating it.**



## What happened

GitLab has a pattern-matching mechanism inside. It is needed, for example, to display files nicely and to check rules in the build settings.

The bug in this mechanism is similar to an old odometer in a car. It shows a maximum of 99,999 kilometers. You drive one more, and the odometer shows zero again. The car has traveled a huge distance, but the device is sure that it is new.

The same thing happens here. An attacker feeds GitLab a specially crafted pattern. The internal counter "overflows" and shows a small number. GitLab allocates a tiny box for the data, but puts a huge load into it. The data spills over the edge and overwrites adjacent memory. Through this, the attacker can run their own code.

The most unpleasant part: the attack requires neither a login nor a password. Researchers write that the attack can be carried out through a specially crafted file that GitLab displays in the browser.

## Why the October 12 update doesn't help

In October, GitLab released two urgent updates in a row:

Date |  Vulnerability |  Fixed versions  
---|---|---  
October 21 |  CVE-2026-110264, 10 out of 10 |  19.5.1, 19.4.3, 19.3.6, 19.2.9, 19.1.9, 19.0.10, 18.11.13  
October 12 |  CVE-2026-97229, 10 out of 10 |  19.4.2, 19.2.8, and other versions released that day  
  
Both bugs live in the same pattern-matching mechanism. But they are different holes. The October 12 update closed the first one, while the second remained.

It's like changing the lock on the front door and not noticing that the window next to it is open too. If you updated GitLab on October 12 and relaxed, your server is still vulnerable.

> In total, the October 21 update closes 11 vulnerabilities. One is critical, the rest are of high, medium, and low severity.

## Who is affected

Your GitLab version |  Vulnerable? |  What to do  
---|---|---  
19.5.0 |  Yes |  Update to 19.5.1  
19.4.0 to 19.4.2 |  Yes |  Update to 19.4.3  
19.3.0 to 19.3.5 |  Yes |  Update to 19.3.6  
19.2.0 to 19.2.8 |  Yes |  Update to 19.2.9  
19.1.0 to 19.1.8 |  Yes |  Update to 19.1.9  
19.0.0 to 19.0.9 |  Yes |  Update to 19.0.10  
18.11.0 to 18.11.12 |  Yes |  Update to 18.11.13  
18.10 and earlier |  Yes |  Update step by step, see the section below  
The version from the "What to do" column or newer |  No |  Nothing  
  
Usually GitLab releases fixes only for the three latest versions. This time it made an exception and released fixes for four more older ones. This is rare and shows how serious the bug is.

> As of October 22, no attacks exploiting this vulnerability have been recorded. But after details are published, it usually takes very little time before bots start scanning all servers one after another.

## Find out your version

**Via the browser.** Log in to GitLab and click the "?" (Help) icon in the menu. The version is shown there. Or open the address `https://ваш-gitlab/help`.

**Via SSH:**
    
    
    sudo gitlab-rake gitlab:env:info | grep -A2 "GitLab information"

Or shorter:
    
    
    cat /opt/gitlab/embedded/service/gitlab-rails/VERSION

**If GitLab is in Docker:**
    
    
    docker exec -it gitlab cat /opt/gitlab/embedded/service/gitlab-rails/VERSION

Instead of `gitlab`, specify the name of your container. Compare the version with the table above.

## Make a backup

GitLab stores the code of the entire team. Be sure to save a copy before updating. It's like taking a photo of documents before taking them to be signed. If something gets lost, you will still have the original.
    
    
    sudo gitlab-backup create

Separately copy the two files with settings and keys. Without them, the backup cannot be restored:
    
    
    sudo cp /etc/gitlab/gitlab.rb /etc/gitlab/gitlab-secrets.json ~/

Do not keep the copies on the same server. For example, download them to your own machine or move them to another storage.

## Update GitLab

The safest path is to update to the fixed version of **your own branch**. For example, from 19.4.1 to 19.4.3, rather than straight to 19.5.1. It's like replacing a wheel with one of the same model, rather than fitting unfamiliar tires before a long trip.

Warn your team: during the update, GitLab will be unavailable for anywhere from a few minutes to half an hour.

The examples below use version 19.4.3. Substitute your own from the table. If you have the paid edition, replace `ce` with `ee`.

**Ubuntu and Debian:**
    
    
    sudo apt update
    sudo apt install gitlab-ce=19.4.3-ce.0

**AlmaLinux and Rocky Linux:**
    
    
    sudo dnf install gitlab-ce-19.4.3

**Docker.** Change the image version in `docker-compose.yml`:
    
    
    image: gitlab/gitlab-ce:19.4.3-ce.0

And restart the container:
    
    
    docker compose pull
    docker compose up -d

**After the update** , check the version as in step 1 and run the GitLab self-check:
    
    
    sudo gitlab-rake gitlab:check SANITIZE=true

Then open GitLab in the browser and make sure that projects, tasks, and builds are working.

## If you have a very old version

For versions 18.10 and earlier, there is no separate fix. You need to upgrade to at least 18.11.13.

But you can't jump over several versions at once. GitLab is updated like a ladder: it has mandatory "steps" that must be passed through in order. It's like climbing to the 10th floor without an elevator. You can't jump from the 3rd straight to the 10th.

What to do:

  1. Open the official GitLab Upgrade Path tool (link at the bottom of the article).
  2. Specify your version and the target one, for example 18.11.13 or newer.
  3. The tool will show all the mandatory steps.
  4. Go through them one by one. Make a backup before each step.



On very old versions, such an update can take several hours. It is better to test it first on a copy of the server.

## Checklist

  * Found out the GitLab version
  * Compared it with the table
  * Made a backup with the command `gitlab-backup create`
  * Copied `gitlab.rb` and `gitlab-secrets.json` to another server
  * Warned the team about a short downtime
  * Updated GitLab to the fixed version of my branch
  * Checked the version and ran `gitlab:check`
  * Made sure that projects and builds work



## Don't want to figure it out yourself?

Updating GitLab scares many people, and not without reason. If something goes wrong, the team will be left without code and builds. And on old versions, you need to go through several mandatory steps without skipping any.

For such cases, Zomro has two options.

### **SOD: we will update GitLab for you**

Our system administrator will:

  * make a backup and save it in a safe place;
  * build an update plan with the necessary steps;
  * update GitLab at a time convenient for you, for example at night;
  * check that projects, tasks, and builds work.



Cost: €12.50 for every 15 minutes of work.

  
[**Order an up**](http://zomro.com/paid-support-services/server-management-services)[**date**](http://zomro.com/rus/paid-support-services/server-management-services)

### Premium: fast help when you need it

If GitLab doesn't come back up after the update, the entire team is at a standstill. With a regular support ticket, a response can take up to 10 hours. With Premium, we respond within 5 to 30 minutes.

New vulnerabilities appear every week. With Premium, you won't have to deal with them alone.

**[Activate Premium](https://zomro.com/paid-support-services)**

Table of contents

  * What is GitLab
  * What happened
  * Why the October 12 update doesn't help
  * Who is affected
  * Find out your version
  * Make a backup
  * Update GitLab
  * If you have a very old version
  * Checklist
  * Don't want to figure it out yourself?



Similar articles:

[How to change the PHP version in the HestiaCP panel?](https://zomro.com/blog/faq/246-kak-smenit-versiju-php-v-paneli-hestiacp) [How to install phpMyAdmin in Docker](https://zomro.com/blog/faq/289-kak-ustanovit-phpmyadmin-v-docker) [How to install and configure MySQL on Windows Server](https://zomro.com/blog/faq/364-how-to-install-and-configure-mysql-on-windows-server) [How to install Nginx in Docker-Compose](https://zomro.com/blog/faq/317-kak-ustanovit-nginx-v-docker-compose) [Connecting to a Windows Server via RDP (Remote Desktop)](https://zomro.com/blog/faq/685-connecting-to-a-windows-server-via-rdp-remote-desktop)

[ Premium Cloud VPS from €7.95/mon ](/premium-vps)

![](/static/site/imagesNew/blogSupport/popup-server.avif?v=1794915141)

ZOMRO / SERVER MANAGEMENT

Need a sysadmin's help? 

Describe the issue and we will get back to you within 15 minutes.

Your name 

Your email 

Phone 

Describe the problem 

LEAVE A REQUEST →  [ ![](/static/site/imagesNew/svg/telegram-btn-icon.svg?v=1794915141) Message us on Telegram ](https://t.me/zomro_sysadmin)

You can find the full list of services and prices on the page [ Server administration and maintenance services. ](/paid-support-services/server-management-services)

Your data has been successfully sent!

Thank you for contacting us. We will get back to you shortly.

Got it! 
