1. Red
  2. Learn
  3. Other incidents

Check your self-hosted GitLab version and upgrade safely

Check your self-hosted GitLab version, find the fixed release for CVE-2026-110264 (CVSS 10.0), and upgrade through the required stops with a backup first.

By Timothy Lindblom, FounderPublished 2 November 20269 min readHow we check facts
On this page
  1. Is my GitLab affected?
  2. How do I check my GitLab version?
  3. Which version should I upgrade to?
  4. How do I prepare so the upgrade does not hurt?
  5. How do I upgrade each install type?
  6. How do I confirm the upgrade worked?
  7. Am I affected? A three-state self-test
  8. Was GitLab exploited, and what should I look for?
  9. What if I cannot upgrade today?

To update self-hosted GitLab for CVE-2026-110264 (CVSS 10.0), read your exact running version, find the fixed release for your line (18.11.13, 19.0.10, 19.1.9, 19.2.9, 19.3.6, 19.4.3 or 19.5.1), back up the database and your secrets file, and upgrade through every required stop. Land on the 29 October builds (19.5.3, 19.4.5, 19.3.7, 19.2.10, 19.1.10, 19.0.11 or 18.11.14) to pick up the later fixes too. Then read the version again from the running instance. GitLab.com was already patched.

10.0CVSS score of CVE-2026-110264
7.0oldest affected version
7fixed releases across 7 lines
12CVEs fixed in the same release
FactDetailSource
CVECVE-2026-110264, CVSS 10.0, criticalGitLab patch notice, 21 October 2026
AffectedGitLab CE and EE, self-managed, from 7.0 up to the patch before the fixed version on each lineGitLab patch notice
Fixed18.11.13 · 19.0.10 · 19.1.9 · 19.2.9 · 19.3.6 · 19.4.3 · 19.5.1GitLab patch notice
Already patchedGitLab.com; Dedicated tenants on 19.3.5-internal0 or 19.4.2-internal0 and laterGitLab patch notice
WorkaroundNone documentedGitLab patch notice
ExploitationTwo detections released; no confirmed exploitation in the notice; CVE-2026-110264 not in the CISA catalogCISA KEV, checked 2 November 2026
Exploited siblingCVE-2026-97229, CVSS 10.0, CI/CD regex compiler overflow, fixed 12 October in 19.4.2, 19.3.5, 19.2.8; added to CISA KEV on 29 October 2026GitLab 19.4.2 notice, CISA KEV
Newest builds19.5.3, 19.4.5, 19.3.7, 19.2.10, 19.1.10, 19.0.11, 18.11.14 (29 October 2026)GitLab patch notice
Checked2 November 2026this page

Is my GitLab affected?

If you run GitLab CE or EE on your own server, container or cluster, and it is older than the fixed release for its line, yes. GitLab describes an integer overflow while compiling a specially crafted regular expression that, under certain conditions, lets an unauthenticated user run code on the server. The affected range starts at 7.0, which GitLab released in 2014. That tells you how far back the range goes. It does not tell you when the flaw was introduced. The bug itself is covered in our CVE-2026-110264 write-up, and if the CVSS score and affected-range wording are new to you, this explainer on CVSS scores and affected ranges explains them.

GitLab.com is not yours to patch. Neither is a Dedicated tenant at the versions in the table above. If another company hosts GitLab for you on a server of its own, that is self-managed from this page's point of view, and the question for them is the running version. Sorting out patching duties with a host covers how to ask.

The same release fixed eleven more CVEs, rated from 8.2 down to 2.7. Those list only 19.3.6, 19.4.3 and 19.5.1 as fixed versions. If you can choose, land on one of those three. The 18.11.13, 19.0.10, 19.1.9 and 19.2.9 builds close the CVSS 10.0 issue and the notice lists no fix for the others on those lines.

How do I check my GitLab version?

Ask the instance that is running, not the file you think you installed. Pick the line that matches your setup.

  • Linux package, on the server. sudo gitlab-rake gitlab:env:info prints the installation details, including the version (GitLab Rake tasks). Self-compiled installs use bundle exec rake gitlab:env:info RAILS_ENV=production.
  • From any machine, as an administrator. The version API returns version and revision for a request carrying a PRIVATE-TOKEN header: GET /api/v4/version.
  • Docker. Read the image tag in your run command or docker-compose.yml, then confirm with the Rake task or the API. A latest tag tells you nothing about which version is inside.
  • Helm. The chart version is not the GitLab version. GitLab says chart versions do not follow GitLab numbering, so look up the mapping for your chart, then confirm with the API.

Write the full version down, including the patch number and the edition (CE or EE). You need all three in the next step.

Which version should I upgrade to?

The smallest move that reaches a fixed build depends on your current line. Required stops matter here. For GitLab 18 and 19, GitLab's upgrade paths place them at 18.2, 18.5, 18.8, 18.11, 19.2, 19.5, 19.8 and 19.11.

You runSmallest move to a fixed buildNote
19.5.019.5.1Same line, one patch
19.4.x below 19.4.319.4.3Also fixes the other eleven CVEs
19.3.x below 19.3.619.3.6Also fixes the other eleven CVEs
19.2.x below 19.2.919.2.919.2 is a required stop. Moving on to 19.3.6 or later also closes the other eleven
19.1.x below 19.1.919.1.9Next stop after it is 19.2
19.0.x below 19.0.1019.0.10Next stop after it is 19.2
18.11.x below 18.11.1318.11.1318.11 is a required stop
18.0 to 18.10Upgrade through the stops to 18.11.13No fix is listed on these lines
17.x or olderFollow the path to 18.11.13Use the upgrade path tool GitLab links

Table checked against the patch notice and the upgrade path page on 24 October 2026. GitLab's maintenance policy says security fixes normally go to the current release and the previous two, which were 19.5, 19.4 and 19.3 at our check. Fixes for 19.0 to 19.2 and 18.11 are the "precedent to backport" case the policy describes for highly severe issues. Expect those lines to be the last to get anything further.

GitLab also says to take the latest patch of the target line, not the first one. At our 2 November check that is the 29 October release: 19.5.3, 19.4.5, 19.3.7, 19.2.10, 19.1.10, 19.0.11 and 18.11.14. It removes trust for the compromised eMudhra intermediate certificates (CVE-2026-111943), runs database migrations, and needs GitLab Runner 19.5.1 plus rebuilt job images that carry their own ca-certificates. GitLab skipped the numbers 19.5.2 and 19.4.4. Run the upgrade path tool that the page links and let it list every stop for your version.

How do I prepare so the upgrade does not hurt?

GitLab's plan your upgrade page asks for the same few things every time. Work through them in order.

  • Take a full backup (sudo gitlab-backup create on a Linux package install).
  • Copy /etc/gitlab/gitlab-secrets.json and /etc/gitlab/gitlab.rb somewhere else. The backup task does not store them, on purpose, because the database holds encrypted 2FA data and CI/CD secure variables and the key must not sit beside them.
  • Note that a backup restores only to exactly the same version and type. Keep the old package or image reachable.
  • Check that background migrations are finished: Admin, Monitoring, Background migrations, or the query in GitLab's migration page. Do not start the next stop while any is active.
  • Run sudo gitlab-rake gitlab:check and confirm sign-in and a repository operation work before you change anything.
  • Pause runners and CI/CD pipelines, and enable maintenance mode if you use it.
  • If you can, rehearse on a clone. GitLab notes this also shows how long migrations take.

If another person or company runs the server, send them this and keep the reply.

For our GitLab at [address], what exact version and edition is running now? Which fixed release will you move us to for CVE-2026-110264, through which required stops, and when? Please confirm a backup that includes gitlab-secrets.json and gitlab.rb, and send the version the running instance reports once you finish.

How do I upgrade each install type?

Six steps: read version, choose target, back up, check migrations, upgrade, confirm running version 1 Readrunning version 2 Choosefixed target 3 Back updata + secrets 4 Migrationsall finished 5 Upgradeeach stop in turn 6 Confirmversion from therunning instance more stops? back to step 4
The upgrade loop. At every required stop, wait for background migrations before the next move. Step 6 is the only step that counts as evidence.

Linux package (Omnibus)

GitLab's package page installs a pinned version. Replace the version with your target and use the CE package name and suffix if you run Community Edition. Upgrade GitLab Runner to match the target afterwards.

sudo apt update && sudo apt install gitlab-ee=<version>-ee.0
sudo dnf install gitlab-ee-<version>-ee.0.el9

GitLab says the package takes an automatic database backup before installing, and still asks you to keep your own full backup. You cannot jump straight to the newest major version when the path has several stops, so repeat the install for each stop.

Docker

GitLab's Docker steps are: back up, stop and remove the container, pull a versioned image such as gitlab/gitlab-ee:<version>-ee.0, and recreate it with the same three volumes (/etc/gitlab, /var/log/gitlab, /var/opt/gitlab). Use a version tag, not latest. With Compose, change the tag in docker-compose.yml, then docker compose pull && docker compose up -d.

Kubernetes (Helm)

Export your values with helm get values gitlab > gitlab.yaml, look up the chart version that maps to your target GitLab version, and run helm upgrade gitlab gitlab/gitlab --version <chart version> -f gitlab.yaml. GitLab warns that skipping minor releases can leave the database schema broken. Single-node and zero-downtime procedures differ, and the patch notice points multi-node installs to the zero-downtime process.

How do I confirm the upgrade worked?

Repeat the version check, after the last stop has finished and the services are back up. Use the API call or sudo gitlab-rake gitlab:env:info, and for containers check that the running container was created from the new image. Then run sudo gitlab-rake gitlab:check, unpause runners and pipelines, and switch maintenance mode off, as GitLab's package page lists.

Keep the output. A line reading the fixed version from the running instance, with a date, is the evidence you can show a client, an auditor or a manager.

Am I affected? A three-state self-test

Am I affected? Where you stand right now

A lookup from outside can match a version string it can see to known vulnerabilities. It cannot see a private instance, a version GitLab hides from visitors, or whether your upgrade finished.

  1. Detected A version you can see, from outside or from your own admin, is below the fixed release for its line. Treat the instance as exposed. Take the backup and begin the upgrade today, internet-facing instances first.
  2. Unknown You cannot read the version, you do not know who runs it, or the image tag is latest. This is the common case. Get the running version from the API or the server before you decide anything.
  3. Confirmed by owner evidence The running instance reports the fixed version or later for its line, read after the upgrade finished. The CVE is closed on that instance. Whether anything reached it earlier is a separate question.

No scan, ours included, moves you from "unknown" to "confirmed".

Was GitLab exploited, and what should I look for?

At our 2 November 2026 check the patch notice reported no confirmed exploitation, and the CISA Known Exploited Vulnerabilities catalog, whose newest entries were dated 30 October, did not list CVE-2026-110264. It does list its sibling. CISA added CVE-2026-97229, the CVSS 10.0 CI/CD regular expression overflow GitLab fixed on 12 October, on 29 October 2026, and notes that the same Ruby/Onigmo flaw can reach other products. Ruby shipped the engine fixes in 4.0.9, 3.4.12 and 3.3.13 on 23 October. Every fixed build in the table above is newer than GitLab's 12 October fix on the 19.2 to 19.4 lines, and GitLab lists only those three lines as affected by it, so one upgrade closes both. GitLab did ship two threat detections for it, named "Onigmo native worker crash" and "Org mode render error burst". Those tell you what GitLab chose to watch for. They are not proof that your instance was reached, and they are not a statement that nobody was.

For an instance that was reachable from the internet while below the fixed version, review web, application and system logs for those events, unexpected administrator accounts, new access tokens or runners, and changes to CI/CD variables. If you find a sign of access, follow the step-by-step breach response. GitLab's database holds CI/CD secure variables, so rotating what a compromised host could read matters; this ordered rotation walkthrough sets the order. The wider list for October is in the October 2026 tracker and the checklist for this week. Other self-hosted tools had their own bad month, such as the Atlassian pre-auth file read, and the other incident write-ups follow the same pattern.

What if I cannot upgrade today?

The notice documents no workaround, so the upgrade stays the fix. If you are stuck behind a change window or a required stop, order the work. Start with the instance people can reach from the internet, then private ones. Ask who truly needs to reach each instance and narrow that with your host or network team. That narrowing is our suggestion and does not replace the upgrade. GitLab's own security guidance puts keeping GitLab up to date on the self-managed administrator.

If you want an outside view of what your public sites show while you work, the free scan reads the stack your site serves and matches each version to known vulnerabilities. It is a lookup. It can say a version is affected, not whether your setup is exposed.

Questions people ask

How do I check which version of GitLab I am running?

Ask the running instance. On a Linux package install, run sudo gitlab-rake gitlab:env:info on the server. From any machine, an administrator can call the version endpoint of the API with a personal access token. For Docker and Helm installs, read the image tag or chart value as well, then confirm it against what the instance reports.

Can I skip versions and go straight to the newest GitLab?

Not if your path has required stops. GitLab says you cannot upgrade directly to the latest major version when the path requires several stops. Upgrade to each required stop in order and let the background migrations finish before the next one. GitLab's upgrade path tool lists the stops for your version.

Is there a workaround if I cannot upgrade today?

GitLab's notice for CVE-2026-110264 documents none. The fix is the upgrade. If you must wait, decide who truly needs to reach the instance and tell your host or network team. That is our suggestion and not a GitLab-documented mitigation.

Does GitLab.com or my managed GitLab need an upgrade?

GitLab says GitLab.com was already running the patched version, and Dedicated tenants on 19.3.5-internal0 or 19.4.2-internal0 or later needed no action. If a company or agency runs GitLab for you on its own server, that is self-managed and you should ask them for the running version.

Was my GitLab already exploited before I upgraded?

GitLab released detections for this issue, and CVE-2026-110264 was not in CISA's catalog at our 2 November check. Its sibling in the same regex engine, CVE-2026-97229, entered the catalog on 29 October as exploited. That does not clear your instance. If it was internet-facing and below the fixed version, review logs and treat any sign of access as a server compromise.

What should I back up before I upgrade GitLab?

Run a GitLab backup and copy gitlab-secrets.json and gitlab.rb separately, because the backup task does not include them. A backup restores only to exactly the same version and type, so keep the old package or image available until the new version has run cleanly.

Sources

  1. GitLab critical patch release 19.5.1, 19.4.3, 19.3.6, 19.2.9, 19.1.9, 19.0.10, 18.11.13 (GitLab Docs, 21 October 2026)CVE-2026-110264, CVSS 10.0, affected and fixed versions, GitLab.com and Dedicated status, detections, no documented workaround. Checked 2 November 2026.
  2. GitLab patch release 19.5.3, 19.4.5, 19.3.7, 19.2.10, 19.1.10, 19.0.11, 18.11.14 (GitLab Docs, 29 October 2026)The newest build on every line. Removes trust for the compromised eMudhra intermediates (CVE-2026-111943), needs Runner 19.5.1, includes database migrations.
  3. GitLab critical patch release 19.4.2, 19.3.5, 19.2.8 (GitLab Docs, 12 October 2026)CVE-2026-97229, CVSS 10.0, the CI/CD regular expression compiler overflow that CISA added to KEV on 29 October 2026.
  4. Ruby: regexp fixes for GitLab CVEs (ruby-lang.org, 23 October 2026)Maps CVE-2026-97229 and CVE-2026-110264 to Onigmo fixes in Ruby 4.0.9, 3.4.12 and 3.3.13.
  5. CVE-2026-110264 (CVE.org record)The record GitLab's notice links. The page did not render its contents for our fetch, so no claim on this page rests on it.
  6. GitLab upgrade paths and required upgrade stops (GitLab Docs)Required stops at x.2, x.5, x.8 and x.11 for GitLab 18 and 19; the upgrade path tool is linked from this page. Checked 24 October 2026.
  7. Plan your upgrade (GitLab Docs)Backups, staging test, background migrations, health checks, runner pause, rollback plan.
  8. Upgrade the Linux package to a specific version (GitLab Docs)Pinned apt and dnf installs, the automatic database backup, runner version matching.
  9. Upgrade GitLab in Docker (GitLab Docs)Versioned tags instead of latest, the three volume mounts, the Compose route.
  10. Upgrade the GitLab Helm chart (GitLab Docs)Chart versions do not match GitLab versions; one minor release at a time.
  11. Check background migrations before an upgrade (GitLab Docs)
  12. Back up GitLab (GitLab Docs)The backup does not include gitlab-secrets.json or gitlab.rb; restore needs the exact same version and type.
  13. GitLab maintenance policy (GitLab Docs)Security fixes go to the current release and the previous two; severe issues can be backported further.
  14. Metadata (version) API (GitLab Docs)
  15. GitLab Rake tasks: environment info and check (GitLab Docs)
  16. CISA Known Exploited Vulnerabilities catalogCVE-2026-110264 was not listed at our 2 November 2026 check. The sibling GitLab regex bug CVE-2026-97229 was added on 29 October 2026.

Facts on this page are dated and point at the primary source next to them. If a vendor status changes after the date shown, the vendor's page wins; tell us at support@run.cloud and we will update it.