Menu

We Upgraded GitLab and Were Still Vulnerable: 7 Lessons From Alpine's CVE-2026-97229 Incident
📰

We Upgraded GitLab and Were Still Vulnerable: 7 Lessons From Alpine's CVE-2026-97229 Incident

DEV Community: gitlab·Lycore Development·18 days ago
#B2H8GYnh
#devtogitlab#devto#dev#gitlab#alpine
Reading 0:00
15s threshold

Alpine Linux published a short, unusually honest incident report this week. Someone tried to exploit a critical GitLab vulnerability on their self-hosted instance. The part that should make every team that self-hosts developer tooling pause is this: they had already upgraded GitLab, and the instance was still vulnerable.

Nobody did anything wildly wrong. They hit a series of small, very normal gaps, the kind most teams have right now. This post walks through what happened (sticking only to what Alpine has published), then turns each gap into something you can check on your own infrastructure this week.

What happened, in short

All of the following comes from the Alpine Linux incident report , published October 28, 2026:

The bug: CVE-2026-97229 is a critical (CVSS 10.0) vulnerability in how GitLab evaluates regular expressions in CI configuration. The underlying flaw is in Onigmo, the regular expression engine built into Ruby.

The fix lives in Ruby, not in GitLab's code.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.