Hacker News
GitLab 19.6.0 is out and still vulnerable to Ruby2Shell and NGINX2Root
They released their usual monthly release 19.6.0 to their package repos (https://packages.gitlab.com/gitlab/gitlab-ee/ubuntu/jammy/pool/main/g/gitlab-ee/) but did not announce it at all as of 3.5h after release (https://docs.gitlab.com/releases/all-releases.xml, https://docs.gitlab.com/releases/19/gitlab-19-6-released/).
But more annoyingly, this release does not address ruby2shell or nginx2root, nor do patches for their older releases exist yet and there's no communication on any of this (that I can find).
root@gitlab:~# cat /opt/gitlab/embedded/service/gitlab-rails/VERSION
19.6.0-ee
root@gitlab:~# /opt/gitlab/embedded/sbin/nginx -version
nginx version: nginx/1.31.7
root@gitlab:~# /opt/gitlab/embedded/bin/ruby --version
ruby 3.3.13 (2026-10-23 revision af48f08f21) [x86_64-linux]
root@gitlab:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.5 LTS
Release: 22.04
Codename: jammy
Multiple MRs were created in their repos 14-15 hours ago, no urgency visible. Heres 2 I found:https://gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/10138
https://gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/10139
pFalken604
|next
[-]
There is also a workaround to disable http2 from NGINX and make that part safe. I'm leaving HTTP2 disabled for the forseeable future. - edit /etc/gitlab/gitlab.rb - add lines: gitlab_rails['nginx']['http2_enabled'] = false nginx['http2_enabled'] = false - save and run: gitlab-ctl reconfigure - finally run: gitlab-ctl restart nginx
There is no workaorund for Ruby2Shell though :( As it was just dropped last night, well after they would have started testing etc for 19.6.0, it's no surprise it's not in there. Also, since they konw 19.6.0 has Ruby2Shell in it, it's not much surprise they haven't been promoting it, or that they are scrambling.
GitLab is such a huge beast that it can't be quick to get changes made and run through tests for everything. Who knows what else the runtime update caused to fail. I imagine they are working on it.. meanwhile I firewalled the web of any of the ones I take care of. IMO having gitlab open to the public web is insanity personified.. I sure wouldn't do that with my instance!