Alpine Linux has rebuilt its GitLab server from scratch after attackers tried to exploit a maximum-severity flaw in the code-hosting platform, the latest sign that a vulnerability disclosed in October is now being used against real targets. The flaw, tracked as CVE-2026-97229, carries the maximum CVSS score of 10.0 and allows an unauthenticated attacker to execute code on a self-managed GitLab server by submitting a specially crafted regular expression in a CI/CD pipeline configuration.
The bug sits not in GitLab's own code but in Onigmo, the regular-expression engine bundled with Ruby. An integer overflow in how Onigmo calculates the size of a compiled pattern can corrupt control flow in the Ruby process that evaluates pipeline configurations. On an instance that allows open self-registration and public projects, researchers say the attack chain needs no login at all.
Eight crashes in two days
According to Alpine, someone registered a new account on its public GitLab instance on October 20 and began feeding it crafted CI files. Workers crashed eight times across October 20 and 21; four attempts got past the initial crash and failed only later, though none appeared to complete. The attacker also downloaded Alpine's GitLab container image, suggesting the exploit was being tuned to that build.
Alpine found no evidence that attackers executed code or tampered with software: repository commits and packages checked out clean. But background job logs and the old container filesystem were gone, and there were no outbound connection records to confirm nothing left the machine. Unable to rule out a compromise, the team closed the instance on October 27 and 28, rebuilt it from scratch, and reset passwords and secret keys. Users were advised to reset their GitLab passwords and re-pull the October 27 image.
The patch that did not patch
Alpine's experience also exposes an awkward trap in this fix. GitLab disclosed the flaw and shipped patches on October 12 in versions 19.2.8, 19.3.5, and 19.4.2. Alpine first upgraded to 19.3.4, one release short of the fix, then moved to 19.3.6 — but the instance stayed exploitable because its custom container image shipped a standard Ruby without the patch. GitLab's remedy arrives as a patch to the Ruby interpreter bundled in its official packages; installations running their own Ruby need a separate upgrade, which upstream Ruby delivered on October 22 and 23. Only the October 27 image, carrying Ruby 3.3.13, closed the hole. The lesson: check the runtime inside the running image, not just the version string on the outside.
CISA's deadline — and why it matters
The incident gained fresh urgency on October 29, when the US Cybersecurity and Infrastructure Security Agency added CVE-2026-97229 to its Known Exploited Vulnerabilities catalog. Under Binding Operational Directive 26-04, federal civilian agencies must remediate listed flaws on exposed assets, and for this entry the deadline is November 1. Private companies are not bound by the directive, but a KEV listing is widely read as a signal: someone has already used the flaw against a real target.
The exposure is broad. Censys counted 25,766 vulnerable hosts and 79,224 vulnerable web properties on October 13, before most patching had taken place. GitLab.com was already patched before disclosure, so the risk sits with self-managed Community and Enterprise Edition installs, which hold source code, pipeline secrets, and deployment credentials. Alpine warned that a successful exploit could have exposed password hashes, two-factor authentication secrets, CI/CD secrets, and private project content, though it stressed none of that was confirmed compromised. A second GitLab regex flaw, CVE-2026-110264, also scores 10.0, so the practical move is to upgrade to the latest point release on your branch.



