Alpine Linux rebuilt its GitLab instance after an attacker came close to exploiting CVE-2026-97229 on October 20 and 21. Its October 28 incident report explains why a subsequent GitLab upgrade still left the server vulnerable: the repair lived in Ruby, which Alpine’s custom image supplied separately.

Evidence status: Alpine-confirmed exploitation attempts; successful code execution remains unresolved. Alpine found eight worker crashes, including four where the attacker progressed partway through the exploit. It found no evidence of attacker code execution, but missing evidence prevented it from ruling that out.

The project therefore treated the instance as compromised, rebuilt it, reset all passwords and replaced GitLab’s secret keys. Public access was still undergoing testing when the report appeared.

Update — November 2, 2026, 04:42 EST: GitLab has reopened

Alpine’s October 30 reopening notice says the rebuilt server is open, running GitLab 19.3.7 with fixed Ruby 3.3.13. This supersedes the earlier account that reopening was pending.

All users must reset their passwords and set up two-factor authentication again. Personal access tokens and old recovery codes no longer work. SSH host keys changed; check the fingerprints in Alpine’s notice before accepting them.

Project maintainers must re-enter CI/CD and scheduled pipeline variable values. Alpine says to assume the old values may have been exposed and use new credentials where possible. It also recommends replacing webhook, mirror and OAuth secrets and re-entering integration credentials.

Update — October 29, 2026, 17:48 EDT: CISA lists CVE-2026-97229 as exploited

CISA’s Known Exploited Vulnerabilities catalog added CVE-2026-97229 on October 29, with dueDate 2026-11-01 and forensicTriage: Yes. The date is a catalog addition, not the October 12 patch date or the beginning of attacks.

This adds CISA’s exploited-vulnerability assessment to the evidence for prioritizing remediation and investigation. It does not resolve whether code execution succeeded on Alpine’s server. Alpine’s rechecked report still describes missing logs, no observed code execution and integrity checks being extended through October 27.

Custom-image operators still need the actual Ruby fix as well as an updated GitLab application. Preserve available incident evidence and review GitLab’s linked detection guidance alongside patch deployment. Organizations subject to CISA’s directive should follow its applicable remediation and forensic-triage requirements; the catalog date is not a universal deadline for every reader.

CISA records ransomware use as Unknown. Keep this entry separate from CVE-2026-110264, the later regex flaw covered on the linked October patch page.

The GitLab version did not identify the Ruby patch

GitLab’s October 12 advisory describes unauthenticated code execution through a crafted regular expression in CI/CD configuration. A regular expression is a text-matching pattern. GitLab lists these affected branches and first fixed application releases:

GitLab branch Affected versions First fixed release
19.2 Before 19.2.8 19.2.8
19.3 Before 19.3.5 19.3.5
19.4 Before 19.4.2 19.4.2

Those fixes include patches to the Ruby shipped in GitLab’s official packages and images. Alpine mistakenly upgraded to 19.3.4 on October 13. Its later move to 19.3.6 on October 22 still used an unpatched, separately supplied Ruby.

For Alpine’s alpinelinux/gitlab:19.3.6 image, the report says to pull the tag again. Its October 27 image contains Ruby 3.3.13; earlier images bearing that same tag, and older tags, remain vulnerable. A familiar tag name alone cannot establish which image is running.

The Ruby maintainers’ October 23 notice recommends Ruby 3.3.13, 3.4.12 or 4.0.9 or later for the complete group of related fixes. Its table is more specific: the bug behind CVE-2026-97229 first received a Ruby 4.0 fix in 4.0.8. Version 4.0.9 also fixes the separate CVE-2026-110264, covered on our October GitLab patch page.

Custom-image and source-build operators need both the supported GitLab update and the appropriate repaired Ruby. Ruby also warns applications that compile attacker-controlled patterns; a regular-expression timeout does not protect against these compilation bugs.

Package integrity checks have a defined time window

Alpine checked repository commits against an external developer clone and all 45 builders. It says packages built from October 20–24 and the October 21 releases came from verified commits. Signing keys were never stored on the GitLab server.

Those checks support its finding of no observed tampering in the checked packages and releases. The instance remained vulnerable until October 27, and Alpine says it is extending the integrity checks through that date. The published verification window should not be silently widened.

The unresolved server exposure is broader. If execution succeeded, an attacker could have reached password hashes, two-factor secrets, CI variables, runner tokens, integration credentials and private repositories. These are conditional exposure categories, not confirmed theft.

Alpine lacked outbound-connection logs. Some background-job logs and the old container filesystem were also gone. A successful exploit could avoid the crashes that made failed attempts visible.

Separate patch verification from account recovery

  • Custom GitLab operators: verify the actual Ruby supplied by the deployed build, as well as GitLab’s application version. Follow supported upgrade paths and replace running vulnerable images.
  • Alpine GitLab users: change any password reused on another service. Follow Alpine’s reopening instructions above to restore account access and verify the new SSH host keys.
  • Incident responders: preserve logs and image evidence before replacement where feasible. Consider the secrets and downstream access a compromised GitLab could expose, rather than treating a successful upgrade as an investigation result.

Alpine’s response also adds outbound and database logging, longer retention and signed release tags. Independent build records helped it check integrity when the potentially compromised server could not supply sufficient assurance.

What the thread adds

In the ranked Hacker News discussion, JLO64 raises the maintenance burden for people building their own images. In reply, milkshakes links Ruby’s upstream notice and highlights its lack of separate Ruby CVE identifiers.

The notice confirms that Ruby had not requested its own identifiers and tells operators to track the GitLab CVEs. A component inventory or scanner keyed only to Ruby-specific CVEs could therefore miss the relevant advisory relationship. This is a tracking concern grounded in the maintainer notice, not evidence that any particular scanner failed.

From a 20-comment thread, in HN’s own order.

Caveat: Alpine supplies the incident evidence and acknowledges missing logs; its package-integrity checks do not establish that no private GitLab data was accessed.