Menu

GitLab 19.3.6 Wasn't Enough for Alpine's Custom Image: Verify Ruby Too
📰

GitLab 19.3.6 Wasn't Enough for Alpine's Custom Image: Verify Ruby Too

DEV Community: gitlab·jamilxt·18 days ago
#Akpx6LJT
#devtogitlab#devto#dev#gitlab#ruby
Reading 0:00
15s threshold

An administrator upgrades GitLab, checks the version, and sees a newer number. The dashboard looks reassuring. But if the deployment uses a custom container with its own Ruby, the vulnerable regular-expression engine may still be running underneath the upgraded application.

That is what happened to Alpine Linux's GitLab instance. The project says it upgraded to GitLab 19.3.6 on October 22, but later found the instance remained vulnerable to CVE-2026-97229. GitLab's fix included patches to the Ruby runtime bundled in official GitLab packages. Alpine's custom image used standard Ruby and did not include that downstream patch. The incident is a useful reminder: application version and dependency patch state are related, but they are not interchangeable. Alpine's incident report explains the gap in detail.

This guide is for teams running GitLab in a custom container or with a separately managed Ruby. It shows how to build an evidence trail for the deployed image instead of treating a version string as proof.…

Continue reading — create a free account

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