Home › Intelligence › Brief
BREACH BRIEF 🟠 High ThreatIntel

Alpine Linux Rebuilds GitLab After Attempted Exploitation of Critical GitLab RCE Flaw (CVE‑2026‑97229)

Alpine Linux detected attempts to exploit GitLab’s CVE‑2026‑97229 RCE vulnerability, rebuilt its GitLab server and reset passwords, and found no evidence of successful code execution. The incident underscores the need for immutable CI/CD audit evidence to satisfy supply‑chain control objectives.

Verisq™ Intelligence · 📅 November 01, 2026 · 📰 bleepingcomputer.com
🟠
Severity
High
TI
Type
ThreatIntel
🎯
Confidence
High
🏢
Affected
3 sector(s)
✅
Actions
3 recommended
📰
Source
bleepingcomputer.com

Alpine Linux Rebuilds GitLab After Attempted Exploitation of Critical GitLab RCE Flaw (CVE‑2026‑97229)

What Happened — On October 20‑21 2026, threat actors attempted to exploit CVE‑2026‑97229, a maximum‑severity integer‑overflow RCE vulnerability in GitLab’s CI/CD regular‑expression compiler (Onigmo). The attackers submitted malicious CI pipeline configurations that repeatedly crashed GitLab worker processes; four of eight attempts came close to successful code execution. Alpine Linux, which hosts its development repositories and CI jobs on a self‑managed GitLab instance, could not confirm whether code was executed because relevant logs were missing and outbound connection records were unavailable. To eliminate any doubt, Alpine rebuilt the GitLab server from scratch, reset all passwords, and upgraded to a fully patched version (GitLab 19.3.6 with the required Ruby patch). No tampering of source code, packages, or signing keys was detected, but the incident highlighted the risk of supply‑chain compromise through CI/CD pipelines.

Why It Matters for Trust & Control Assurance — The episode tests the control objective of maintaining a secure software supply chain and immutable CI/CD audit evidence.

Who Is Affected — Cloud‑infrastructure providers, open‑source project maintainers, and organizations that rely on GitLab‑based CI/CD pipelines.

Recommended Actions

  • Verify that all CI/CD tools run the latest patched versions and that custom container images include upstream security fixes.
  • Implement immutable, centrally retained logs for CI pipeline execution and GitLab activity to provide defensible audit evidence.
  • Conduct a supply‑chain risk assessment of your build environment and enforce code‑signing verification.

Technical Notes

  • Attack vector: Vulnerability exploit via crafted regular expressions in CI/CD pipeline configuration.
  • CVE: CVE‑2026‑97229 (GitLab CI/CD Onigmo integer overflow).
  • Potentially exposed data: User accounts, password hashes, 2FA secrets, CI/CD secrets, integration credentials, private repository content.
  • Status: No confirmed breach; Alpine Linux rebuilt GitLab and reset credentials.

Source: BleepingComputer

📰 Original Source
https://www.bleepingcomputer.com/news/security/alpine-linux-rebuilds-gitlab-after-attempted-rce-attack/ ↗

This Verisq Intelligence Brief is an independent analysis. Read the original reporting at the link above.

Third-party risk

Does this breach reach you?

Verisq continuously monitors your vendors for breach and ransomware activity, so the question stops being whether it happened and becomes whether it reaches you.

See a live Trust Center →