All Posts

Cybersecurity

CISA Lists CVSS 10.0 GitLab Flaw CVE-2026-97229 as Actively Exploited

CISA Lists CVSS 10.0 GitLab Flaw CVE-2026-97229 as Actively Exploited

TechShorts Newsroom

Editorial Team

The US Cybersecurity and Infrastructure Security Agency (CISA) has added CVE-2026-97229, a remote code execution flaw in self-managed GitLab, to its Known Exploited Vulnerabilities (KEV) catalog. GitLab shipped fixes on 12 October. Those fixes are not enough for every server: the bug sits in Ruby's regular expression engine, so installations that run their own Ruby also need a separate Ruby upgrade.

What GitLab disclosed

GitLab's 12 October critical patch release says CVE-2026-97229 could have allowed an unauthenticated user to execute arbitrary code on the GitLab server via a specially crafted regular expression in a CI/CD configuration. GitLab describes it as an integer overflow in the CI/CD regular expression compiler of GitLab Community Edition and Enterprise Edition, and rates it 10.0 under CVSS 3.1, the maximum score.

Affected versions are 19.2 before 19.2.8, 19.3 before 19.3.5 and 19.4 before 19.4.2. GitLab.com was already running the patched version and GitLab Dedicated tenants were patched before the release, so the exposure is in self-managed installations. The advisory lists six threat detections for exploitation attempts.

The KEV listing

CISA's update added two entries, the GitLab flaw and CVE-2026-76418 in Cisco Secure Firewall ASA and FTD software, and gave US federal civilian agencies until 1 November to remediate, Security Affairs reported. That deadline binds only those agencies, under Binding Operational Directive 22-01. Private organisations are also advised to review the KEV catalog and fix listed flaws in their own systems.

Alpine Linux's account of an attack

Alpine Linux published a detailed account of an attempt against its self-hosted GitLab. On 20 and 21 October, a newly registered account sent crafted CI configurations to the instance, crashing GitLab worker processes eight times. The instance was still on GitLab 19.3.4, because on 13 October Alpine had upgraded to 19.3.4 instead of 19.3.5, which carried the fix, by mistake.

Alpine said it found no evidence the attack succeeded but could not rule it out, so it treated the instance as compromised and rebuilt it from scratch. It said the aports repository, packages and its 21 October releases were not tampered with, and that the keys that sign Alpine packages and releases are not, and never have been, stored on the GitLab server.

The instance has reopened on GitLab 19.3.7 with Ruby 3.3.13. Users must set new passwords, set up two-factor authentication again, accept new SSH host keys and create new access tokens.

Why upgrading GitLab may not close it

Alpine's upgrade to GitLab 19.3.6 on 22 October did not fix the vulnerability. The fix is a patch to the Ruby that GitLab bundles, and GitLab applies it only in its official packages and container images. Alpine's image used standard Ruby, so it did not get the patch, and the project found the instance still vulnerable on 26 October.

The Ruby project released Ruby 4.0.9, 3.4.12 and 3.3.13 on 23 October with fixes for bugs in Onigmo, its regular expression engine. Its advisory ties those fixes to four GitLab CVEs: CVE-2026-89078, CVE-2026-93577, CVE-2026-97229 and CVE-2026-110264. Ruby says the bugs are reached only when an application compiles a regular expression from attacker-controlled input, and that Regexp.timeout does not protect against them.

GitLab's 21 October advisory says installations that use their own Ruby runtime, such as self-compiled installs or custom container images, must also upgrade Ruby to 3.3.13, 3.4.12, 4.0.9 or later. Ruby has not requested its own CVE identifiers for these fixes and asks users to track them by GitLab's CVEs. A scanner that checks only GitLab version numbers may therefore miss an outdated Ruby underneath.

A second critical flaw with a wider range

On 21 October GitLab shipped another critical patch release, for CVE-2026-110264. GitLab describes it as an integer overflow that could let an unauthenticated user execute arbitrary code when the server compiles a specially crafted regular expression. It also scores 10.0.

Its reach is wider. All versions from GitLab 7.0 are affected until 18.11.13, 19.0.10, 19.1.9, 19.2.9, 19.3.6, 19.4.3 or 19.5.1, depending on the branch. Servers that took only the 12 October fixes remain exposed to it. The KEV update reported on 30 October covers CVE-2026-97229 only. GitLab lists two detections for CVE-2026-110264 attempts, including one for Onigmo native worker crashes.

What administrators should check

  • On the 19.2, 19.3 and 19.4 branches, 19.2.8, 19.3.5 and 19.4.2 fix CVE-2026-97229. The 21 October releases are the earliest that fix both flaws.
  • Official GitLab Linux packages and container images include the patched Ruby. Self-compiled installs and custom images also need Ruby 3.3.13, 3.4.12, 4.0.9 or later.
  • Alpine lists what could have been exposed had the attack succeeded, including CI/CD variables, runner tokens, 2FA secrets, and webhook, integration and push mirror credentials. That list is a starting point for teams deciding what to rotate after a suspected attempt.

What to watch

The open question is whether CISA adds CVE-2026-110264 to KEV, which would mean it has evidence that the wider-reaching flaw is also being exploited. Alpine says its GitLab stayed vulnerable until it closed the instance on 27 October, and it is extending its tamper checks to that date.

Sources

  • GitLab. "GitLab Critical Patch Release: 19.4.2, 19.3.5, 19.2.8." 2026. https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-4-2-released/
  • GitLab. "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." 2026. https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-1-released/
  • Security Affairs. "U.S. CISA adds GitLab and Cisco flaws to its Known Exploited Vulnerabilities catalog." 2026. https://securityaffairs.com/202133/security/u-s-cisa-adds-gitlab-and-cisco-flaws-to-its-known-exploited-vulnerabilities-catalog.html
  • CISA. "Known Exploited Vulnerabilities Catalog." https://www.cisa.gov/known-exploited-vulnerabilities-catalog
  • Alpine Linux. "GitLab security incident: attempted exploitation of CVE-2026-97229." 2026. https://alpinelinux.org/posts/GitLab-security-incident-CVE-2026-97229.html
  • Alpine Linux. "GitLab is back: what you need to do." 2026. https://alpinelinux.org/posts/GitLab-reopened-after-security-incident.html
  • Ruby. "Regexp compilation fixes related to GitLab's CVE-2026-89078, CVE-2026-93577, CVE-2026-97229 and CVE-2026-110264." 2026. https://www.ruby-lang.org/en/news/2026/10/23/regexp-fixes-for-gitlab-cves/