Alpine Linux reopened its GitLab server on Oct. 29 after rebuilding it from scratch. The new server runs GitLab 19.3.7 with Ruby 3.3.13, which includes a fix for the vulnerability an attacker tried to exploit on Oct. 20 and 21.
In its incident report, Alpine identified the flaw as CVE-2026-97229, a maximum-severity vulnerability in how GitLab processes regular expressions in CI configurations. Alpine said a newly registered account submitted crafted configurations that crashed GitLab worker processes eight times. In four crashes, the attacker got partway through the exploit before failing at the next step. The attacker also downloaded Alpine’s GitLab container image, which Alpine said suggests they were tuning the exploit to its build.
Alpine found no evidence that the attacker ran code on the server, but said it cannot rule that out. Some logs from the attack day are gone, and outbound connections were not logged. Alpine said its checks found no tampering with the aports repository, packages or Oct. 21 releases. Those checks, run Oct. 24, covered commits through Oct. 22 and packages built through Oct. 24; Alpine said it was extending them because the server remained vulnerable until it closed on Oct. 27.
Why the GitLab upgrade was not enough
Alpine said its Oct. 22 upgrade to GitLab 19.3.6 left its custom container image vulnerable. The image used standard Ruby rather than the patched Ruby bundled with GitLab’s official packages. Ruby’s Oct. 23 release notice confirms that Ruby 3.3.13 includes regular-expression compilation fixes related to the GitLab flaw. Alpine advises anyone running GitLab with their own Ruby to upgrade Ruby to 3.3.13, 3.4.12, 4.0.9 or later as well as upgrading GitLab.
The reopening notice says accounts, projects, issues and merge requests remain, but all passwords and two-factor authentication have been reset. Users who sign in with a GitLab password need to set a new one; signing in with GitHub, GitLab.com or postmarketOS still works. Two-factor authentication must be set up again for all accounts. Old personal access tokens no longer work. Project maintainers must re-enter CI/CD variable values and replace secrets that may have been exposed; the notice does not establish that those secrets were stolen.
Comments