Ruby2Shell and Nginx2Root response

AI-generated summary

A critical security announcement by david details urgent updates for Discourse installations due to newly disclosed vulnerabilities in Ruby and Nginx. Users of managed Discourse hosting do not need to take action, as the platform has already updated Ruby to version 4.0.10 and applied Nginx patches. However, self-hosted users are strongly urged to update immediately via /admin/update or a CLI rebuild. To verify the patch, users should check that their base image version is 2.0.20261119 or higher, which ensures Ruby 4.0.10 and a patched Nginx are installed. Several vulnerability IDs for both Ruby and Nginx are listed in the original post.

Clarifications followed regarding the verification process. Jonathan5 noted confusion when cat /VERSION returned exactly 2.0.20261119 after a rebuild, despite Docker images showing a higher tag like 2.0.20261119-0203. david acknowledged this and clarified that the requirement is “2.0.20261119 or higher.”

peternlewis raised a concern where the admin dashboard showed the app as up-to-date (2026.7.6), but cat /VERSION displayed 2.0.20260803, an older base image. supermathie explained that /VERSION reflects the Docker base image version, not the Discourse application version. peternlewis sought further guidance, noting their system still reported Ruby 3.4.10 and Nginx 1.30.4, implying the security patches were not applied despite the dashboard status. This highlights the importance of performing a full rebuild to update the underlying Docker base image, rather than relying solely on the application version check.

Critical vulnerabilities have been disclosed this week in NGINX and Ruby.

If you use our managed discourse.org hosting, no action is required. Ruby has been updated to 4.0.10. Our particular use of Nginx was not vulnerable, but we have applied the patches for defense-in-depth.

If you self-host Discourse, you should update as soon as possible. In a standard install, visit /admin/update and follow the instructions to perform a CLI rebuild.

Verify successful update

If you’d like to verify you have the latest version of our docker image, run these commands:

./launcher enter app
cat /VERSION

If the image version is 2.0.20261119 or higher, then you have the fixed version of Ruby (4.0.10), and a patched version of NGINX.

Vulnerability IDs are:

  • Ruby (advisory): GHSA-34m4-m9fh-gqp5, GHSA-7x2q-68qv-6p8x, GHSA-87fm-7w84-j2px, GHSA-wpqw-5qxg-m68r, GHSA-3p8q-wmhx-vm2w, GHSA-7whj-cfh7-xgm4, GHSA-pvgc-g7gj-pv6h.

  • NGINX (advisories): CVE-2026-123007, CVE-2026-123633, CVE-2026-123634, CVE-2026-121810, CVE-2026-113425, CVE-2026-118899, CVE-2026-123640, CVE-2026-125283.

25 Likes

After rebuild that command showed exactly 2.0.20261119, which initially confused me, but

  • docker images discourse/base shows discourse/base:2.0.20261119-0203 (which I guess counts as greater than 2.0.20261119)
  • ruby -v (inside the container) shows ruby 4.0.10 (2026-11-19 revision a704b7cd95) +PRISM \[x86_64-linux\]
  • nginx -v (inside the container) shows nginx version: nginx/1.26.3
1 Like

Right, my mistake. I’ve updated the OP to:

4 Likes

I run self hosted, and the Dashboard shows it up to date (2026.7.6), but cat /VERSION returns 2.0.20260803 which seems concerning.

image

Am I missing something?

/VERSION holds the base image version, not the application version

What’s the difference? The original post says:

So what do I need to do to correct this? Currently it shows:

root@forum-app:/var/www/discourse# cat /VERSION
2.0.20260803
root@forum-app:/var/www/discourse# ruby -v
ruby 3.4.10 (2026-06-30 revision 2b0b7728dc) +PRISM [x86_64-linux]
root@forum-app:/var/www/discourse# nginx -v
nginx version: nginx/1.30.4