Skip to main content
All incident reports
Incident report

GitLab maximum-severity flaw CVE-2026-97229 exploited against Alpine Linux server

An attacker tried to break into the Alpine Linux project's own GitLab server using CVE-2026-97229, a maximum-severity GitLab flaw fixed on 12 October. Alpine found no evidence the attempt worked but could not rule it out, so it rebuilt the server, reset every password and replaced its secret keys.

· First published

The short version

  • The flaw. CVE-2026-97229 carries a CVSS score of 10.0 and could let an unauthenticated user run code on a GitLab server through a crafted regular expression in a CI configuration. GitLab fixed it on 12 October in 19.4.2, 19.3.5 and 19.2.8.
  • The attack. A newly registered account sent crafted CI configurations to Alpine Linux's GitLab server on 20 and 21 October, crashing worker processes. Alpine blocked the account on 23 October and the attacker returned on 25 and 26 October without success.
  • The rebuild. Alpine's 22 October upgrade to GitLab 19.3.6 did not close the flaw because it sits in Ruby. Alpine shut GitLab to all but developers and build servers on 27 October, finished rebuilding on 28 October, reset all passwords and replaced GitLab's secret keys.
  • What is not known. Alpine found no sign that code ran, but says a successful exploit would leave no trace and some logs are gone, so it treated the server as compromised. It has not said whether runner tokens, CI/CD variables, access tokens or integration credentials were replaced.
  • Wider exposure. CISA added CVE-2026-97229 to its Known Exploited Vulnerabilities catalogue after confirming exploitation. Shadowserver tracks nearly 2,800 internet-exposed GitLab Community Edition instances and does not say how many are patched.

Timeline

DateEvent
12 OctGitLab publishes its advisory and patches CVE-2026-97229 in 19.4.2, 19.3.5 and 19.2.8.
13 OctRapid7 publishes proof-of-concept exploit code for the flaw.
13 OctAlpine upgrades its GitLab server to 19.3.4 rather than 19.3.5, which it later calls a mistake.
20 OctA newly registered account begins probing Alpine's GitLab server.
20-21 OctThe account sends crafted CI configurations that crash GitLab worker processes.
22 OctAlpine upgrades to GitLab 19.3.6, which does not fix the flaw because the server runs standard Ruby.
23 OctAlpine blocks the attacker's account.
25-26 OctThe attacker returns and tries to regain access, without success.
26 OctAlpine finds the server is still vulnerable.
27 OctAlpine closes GitLab to everyone except developers and build servers and starts rebuilding it.
28 OctThe rebuild finishes and Alpine discloses the attack.
OctoberCISA adds CVE-2026-97229 to its Known Exploited Vulnerabilities catalogue, saying it has confirmed exploitation.

How the attack on Alpine's server unfolded

Alpine Linux said an attacker tried to exploit CVE-2026-97229 on gitlab.alpinelinux.org, the server that hosts aports, the repository from which its packages are built. The server was on GitLab 19.3.4, which Alpine installed on 13 October instead of 19.3.5 and calls a mistake. It was still on that version, without the 12 October fix, when a newly registered account began probing the server on 20 October.

The account sent crafted CI configurations on 20 and 21 October. They crashed GitLab worker processes eight times, and the main attack on 21 October also produced 502 errors and failed CI jobs. In four of the crashes the attacker got partway through the exploit and failed at the next step, Alpine said. The attacker also downloaded Alpine's GitLab container image. Alpine blocked the account on 23 October; the attacker returned on 25 and 26 October and failed.

On 26 October Alpine found the server was still vulnerable after its 22 October upgrade to 19.3.6. The next day it closed GitLab to everyone except developers and build servers and began a rebuild, which finished on 28 October. Alpine reset every account's password and replaced GitLab's secret keys; the rebuilt server runs Ruby 3.3.13 or later and was being tested before reopening. SecurityWeek reports automated login attempts using passwords compromised in other leaks.

Why upgrading GitLab was not enough

GitLab compiles the regular expressions in CI configurations with Ruby, and the bug is in Onigmo, the regular expression engine built into Ruby. GitLab's 12 October release fixed it by patching the Ruby inside GitLab's own Linux package and container images. Ruby's fixed versions came out on 22 and 23 October. A GitLab upgrade does not change a server's own Ruby, so an install on standard Ruby stays vulnerable, as Alpine found.

BleepingComputer describes the weakness as an integer overflow in the CI/CD regular expression compiler. GitLab's advisory describes insufficient regular expression validation and says that, under certain conditions, an unauthenticated user could have executed arbitrary code. GitLab.com and GitLab Dedicated are already patched. As of 29 October, GitLab's patch posts did not tell self-compiled administrators to update Ruby, and its self-compiled guide still listed Ruby 3.2, which reached end of life in April and will get no fix.

Rapid7 built a working exploit and published proof-of-concept code on 13 October. It ran commands as GitLab's git user on an unpatched official 19.4.1 image but not on the patched 19.4.2 image. That route needs write access first: a malicious .gitlab-ci.yml file and a file path with UTF-8 characters committed to a branch of a public project. The requirement does not apply where new users can register themselves and create projects, and Rapid7 says only the final CI lint request is unauthenticated.

What could have been exposed and who is still at risk

Alpine found no sign that the attacker's code ran: timing probes showed no delays, there were no unexpected files, keys, hooks or processes, and no private data was returned through any web or API request. It cannot be sure, because a successful exploit would leave no crash and no trace in the web logs, some logs from the attack day are gone and neither Alpine nor its hosting provider logged outbound connections. It treated the server as compromised.

Had the attack worked, Alpine says, the exposed data could have included users' email addresses, names and IP addresses, password hashes, two-factor authentication secrets, CI/CD variables and runner tokens, webhook, integration and push mirror credentials, hashed personal access tokens, private repositories and confidential issues and merge requests. The keys that sign Alpine's packages and releases have never been on the GitLab server. Alpine checked aports changes added from 20 to 22 October against a developer's copy of the repository and all 45 build servers, and said packages built from 20 to 24 October and the 21 October releases came from aports changes verified against records outside GitLab; it is extending the checks to 27 October.

Shadowserver tracks nearly 2,800 internet-exposed GitLab Community Edition instances and does not say how many have been secured. CISA added CVE-2026-97229 to its Known Exploited Vulnerabilities catalogue after confirming it is exploited, and encouraged all security teams, including in the private sector, to prioritise patching. BleepingComputer notes the flaw follows several other maximum-severity GitLab issues this year. GitLab has released threat detections for self-managed instances.

What is not known yet

  • Whether the attacker's code actually executed on gitlab.alpinelinux.org.
  • Who carried out the attack and where they were located.
  • Whether runner tokens, CI/CD variables, access tokens and integration credentials stored on the GitLab server have been replaced.
  • How the attacker's CI configurations reached GitLab, and whether new accounts could create public projects on Alpine's server.
  • How many internet-exposed GitLab instances remain unpatched.

What to do

If you run GitLab with your own Ruby

  1. Upgrade GitLab to a fixed release for your version branch as listed in GitLab's advisory.
  2. Update the underlying Ruby to 3.3.13, 3.4.12, 4.0.9 or later, because Alpine says upgrading GitLab alone is not enough.
  3. If you use Alpine's alpinelinux/gitlab image, pull 19.3.6 again.
  4. Check whether you are still on Ruby 3.2, which reached end of life in April and will get no fix.

If you run a packaged or managed GitLab instance

  1. Apply the patched GitLab release for your branch.
  2. Turn on the threat detections GitLab released for self-managed instances.
  3. Check logs for crashed worker processes, 502 errors and failed CI jobs, and for CI configurations pushed by newly registered accounts.
  4. Review whether self-registration and public project creation are open on your instance.

For everyone else

  1. Find internet-exposed GitLab servers on your estate and confirm their patch level, given nearly 2,800 Community Edition instances are tracked online.
  2. Prioritise patching this flaw, as CISA has urged all security teams to do.

Update log

  • First published.

Sources

New incident reports by email

One email a week with the reports published since the last one.

Want us to look at your domain?

Give us one apex domain and we'll send back a written snapshot of what is already visible from outside. No call required.