GitLab CVE-2026-97229: unauthenticated remote code execution, CVSS 10.0

Venus Yazılım4 min read

CVE-2026-97229 in GitLab CE and EE (CVSS 10.0) can allow code execution without login under certain conditions. Upgrade to 19.2.8, 19.3.5, or 19.4.2.

If you run a self-managed GitLab instance, this flaw may let someone outside your organization take it over without logging in. CVE-2026-97229 has a CVSS score of 10.0, and CISA has added it to its Known Exploited Vulnerabilities catalog after evidence of active exploitation. Check your version today.

Short answer: CVE-2026-97229 lets an unauthenticated attacker execute code on GitLab CE and EE servers under certain conditions. It affects versions before 19.2.8, before 19.3.5, and before 19.4.2. The cause is weak validation of regular expressions in CI/CD configuration, which leads to an integer overflow. NVD and GitLab both score it CVSS 10.0. Self-managed GitLab should move to 19.2.8, 19.3.5, or 19.4.2. GitLab.com and GitLab Dedicated are already patched.

At a glance

Field Detail
CVE CVE-2026-97229
CVSS 10.0 (v3.1), as scored by NVD and GitLab. Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Weakness type Integer overflow or wraparound (CWE-190) in the CI/CD regex compiler
Authentication Not required. No user interaction.
Active exploitation Listed in CISA KEV. The Hacker News reports that CISA cited an incident at Alpine Linux.
CISA KEV added 29 October 2026. Due date for federal agencies: 1 November 2026.
Fixed versions 19.2.8, 19.3.5, 19.4.2. GitLab released them on 12 October 2026.

What happened?

When GitLab compiles regular expressions (regex) found in CI/CD pipeline configuration, it does not validate the input well enough. This can trigger an integer overflow. The KEV entry says the underlying issue is a Ruby/Onigmo integer overflow in the CI/CD regex compiler. Under certain conditions, an unauthenticated attacker can then run code on the GitLab server.

The clearest real-world example comes from Alpine Linux. According to The Hacker News, an unknown attacker tried to exploit Alpine’s unpatched GitLab instance on 20 and 21 October 2026. Crafted CI configurations crashed GitLab worker processes eight times. The attacker also downloaded Alpine’s GitLab container image. Alpine found no evidence that the attack succeeded, but it could not rule that out. It treated the instance as compromised and rebuilt it from scratch.

Who is affected?

  • Affected: Self-managed GitLab CE and EE versions 19.2.0 through 19.2.7, 19.3.0 through 19.3.4, and 19.4.0 through 19.4.1.
  • Not affected: 19.2.8, 19.3.5, 19.4.2, and later. GitLab.com and GitLab Dedicated are already patched.
  • The NVD entry does not list versions before 19.2. Even so, moving to a patched branch is the safer choice.
  • The KEV entry notes that other products may be affected by the same Ruby/Onigmo issue. If you run Ruby applications, read Ruby’s advisory.

What should you do?

  1. Check your version. On the GitLab server:
sudo gitlab-rake gitlab:env:info

You can also check the /help page in the administrator interface. If you run GitLab with Docker or Helm, match the image version to the fixed release.

  1. Upgrade to the fixed release. If you run 19.2, move to 19.2.8. For 19.3, move to 19.3.5. For 19.4, move to 19.4.2. GitLab’s release notes link to the upgrade guides.

    • Single-node installations have downtime, because migrations must finish before GitLab starts.
    • Multi-node installations can upgrade with zero downtime.
    • Version 19.3.5 includes post-deploy migrations.
  2. If you cannot upgrade right away. GitLab’s release notes give no workaround for this CVE. They point only to the upgrade guides and to six detection signatures. We recommend restricting access to the instance, for example by placing it behind a VPN or an IP allowlist. This is our general advice, not a vendor workaround.

  3. Check again after patching. If anything looks suspicious, consider rebuilding the instance from scratch, as Alpine did.

Have I been hit?

The sources point to these signs:

  • Repeated crashes of GitLab worker processes. The Alpine incident recorded eight.
  • Unusual CI configurations and the pipelines they create.
  • Unexpected downloads of the GitLab container image.
  • The GitLab release notes list six detection signatures, including “Onigmo native worker crash” and “ci regexp guard rejection”. Check the release notes to confirm which log files these signatures appear in.

Search GitLab logs (on Omnibus installations, usually under /var/log/gitlab/) and your reverse proxy’s access logs. The sources do not publish file hashes or IP addresses.

Frequently asked questions

I use GitLab.com. Do I need to do anything?

No. GitLab says GitLab.com and GitLab Dedicated are already patched. If you run a self-managed instance, follow the steps above.

My GitLab runs only on an internal network. Should I still patch?

Yes. NVD says the attack works under certain conditions, but it does not describe those conditions in detail. Limiting access reduces the risk, but it is not a reason to delay the patch.

Do other Ruby-based applications share this risk?

The KEV entry says the same underlying Ruby/Onigmo issue may affect other products. Read Ruby’s regex fix announcement from 23 October 2026 and check your own use of Ruby regular expressions.

Sources

If you run GitLab on your own server and want help with upgrades or server hardening, take a look at our server management service.

More notes

  1. 4 min read

    Google Brotli CVE-2026-111497: memory overflow in Node.js and Brotli libraries

    A memory overflow in the Brotli decoder (CVE-2026-111497) can lead to code execution without logging in. Update Node.js and Brotli.

  2. 5 min read

    Cisco ASA and FTD CVE-2026-76418: SSL VPN reload flaw and fixed releases

    Unauthenticated attackers can reload Cisco ASA and FTD devices through SSL VPN when secondary authentication is set. It is being exploited. Check and upgrade.

Let’s reserve a slot in the rack.

Describe your project in a few steps and we’ll prepare a written proposal with scope, timeline and an infrastructure plan.

Request a quoteor write directly: email address