Steve Miller's Blog

Attackers Tried to Exploit a Max-Severity GitLab Flaw Against Alpine Linux’s Own Server: A Patch-Now Checklist for Teams Running Self-Hosted Dev Platforms

Three DevOps and security professionals review a development platform status together at laptops in a modern office.

A self-hosted Git server holds your source code, your CI secrets, and often the credentials that touch everything you ship. So when an open-source Linux distribution’s own GitLab instance becomes the test target, everyone else running one should pay attention. A GitLab vulnerability exploited in the wild means every self-hosted team needs to patch, and the most useful lesson in it is a twist almost nobody expected: Alpine Linux upgraded GitLab and was still vulnerable.

The Flaw

GitLab’s October 12, 2026 critical patch release fixed CVE-2026-97229, rated Critical with a CVSS score of 10.0. GitLab describes it as an integer overflow in the CI/CD Regular Expression Compiler that “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.” Affected versions are 19.2 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2. GitLab says GitLab.com and GitLab Dedicated were already patched and urged all self-managed installations to upgrade “immediately.” GitLab also published six threat detections for self-managed customers to spot exploitation attempts.

On October 29, CISA added CVE-2026-97229 to its Known Exploited Vulnerabilities catalog with a November 1 remediation deadline for federal agencies under Binding Operational Directive 26-04, as BleepingComputer reported. CISA’s entry notes that other products can be affected by the same underlying Ruby regex issue. BleepingComputer also noted that Shadowserver tracks nearly 2,800 internet-exposed GitLab Community Edition instances.

What Happened at Alpine

Alpine Linux published its own incident report on October 28, titled “attempted exploitation of CVE-2026-97229.” According to Alpine, on October 20 and 21, “a newly registered account sent crafted CI configurations to our GitLab instance,” which was still running 19.3.4 without the fix. That crashed GitLab worker processes 8 times. “In 4 of those crashes the attacker got partway through the exploit and failed at the next step.” The attacker also downloaded Alpine’s GitLab container image, which Alpine said “suggests they were tuning the exploit to our exact build.”

Alpine’s bottom line is careful, and I will keep it that way: “We have found no evidence that it succeeded, but we cannot rule it out, so we treated the instance as compromised and rebuilt it from scratch.” Alpine says it found no sign of tampering in its aports repository or releases, and that the keys that sign packages and releases have never been stored on the GitLab server.

The Twist: Upgrading GitLab Was Not Enough

Alpine upgraded to GitLab 19.3.6 on October 22. That did not fix the hole. In Alpine’s words, “The fix isn’t in GitLab’s own code but in a patch to Ruby, which GitLab applies only in its official packages. Our image used standard Ruby, so it didn’t get the patch.” GitLab’s release notes do list Ruby regexp patches for each fixed version. Upstream Ruby shipped the fix on October 23, in Ruby 3.3.13, 3.4.12, and 4.0.9.

Alpine’s guidance for everyone else is direct: “If you run GitLab with your own Ruby (from source or in your own container image) rather than GitLab’s packages, upgrading GitLab is not enough: you also need Ruby 3.3.13, 3.4.12, 4.0.9 or later.” Alpine also admits that on October 13 it upgraded to 19.3.4 instead of 19.3.5 “by mistake.” I respect that candor. It is exactly the kind of slip that happens on any busy team.

Why Alpine Could Not Be Sure

This part should make every operator check their logging. Alpine says a successful exploit “would leave no crash and no trace in the web logs.” Some logs from the attack day were gone, and “we had no logging of outbound network connections, and our hosting provider keeps none either.” If the attack had worked, Alpine lists what could have been exposed, including password hashes, 2FA secrets, CI/CD variables and runner tokens, webhook and mirror credentials, and private repositories.

A Self-Hosted Patch Checklist for the Exploited GitLab Vulnerability

These are my recommendations, built on GitLab’s and Alpine’s guidance. They are not an official checklist from either.

  1. Confirm your version against GitLab’s advisory. You need 19.2.8, 19.3.5, 19.4.2, or later. Double-check the exact number. Alpine’s 19.3.4-versus-19.3.5 slip is easy to repeat.
  2. Check your Ruby if you do not use GitLab’s official packages. Source installs and custom container images need Ruby 3.3.13, 3.4.12, 4.0.9, or later, per Alpine. Verify the Ruby version inside the running container, not just your build file.
  3. Deploy GitLab’s published detections. Worker crashes tied to the CI regex compiler are your early warning. Alpine’s first signal was crashes.
  4. Review recent sign-ups and CI lint activity. Alpine’s attacker used a newly registered account. If open registration is enabled on an internet-facing instance, ask whether it needs to be.
  5. Start logging outbound connections from the GitLab host now. Without egress logs, you cannot prove a negative. Keep logs longer than two weeks. Alpine says it is moving past 14 days.
  6. If you were exposed and cannot rule out compromise, rotate. Runner tokens, CI/CD variables, personal access tokens, webhook and mirror credentials, and user passwords. Alpine reset all passwords and replaced GitLab’s secret keys.
  7. Keep signing keys off the Git server. Alpine’s best decision was made long before this incident.
  8. Reduce exposure. If your instance does not need to be public, put it behind a VPN or identity-aware proxy.

Picture this hypothetical: your team patched GitLab last week and closed the ticket. Your instance runs in a custom image on stock Ruby. By Alpine’s account, you may still be exposed, and your web logs would not tell you.

The Bottom Line

CISA now lists this CVSS 10.0 flaw as exploited, and Alpine’s report shows an attacker came close against a well-run open-source project. Alpine found no evidence of success but could not rule it out. Patch GitLab, verify Ruby, turn on egress logging, and decide now what you would rotate if you could not prove a negative.

Exit mobile version