Ruby2Shell and Nginx2Root response

AI-generated summary

david announced critical vulnerabilities in NGINX and Ruby (referenced as “NGINX2ROOT” and “RUBY2SHELL”). Managed hosting on discourse.org required no action, as Ruby was updated to 4.0.10 and NGINX patches were applied. Self-hosted instances were urged to update immediately via /admin/update and a CLI rebuild.

A command cat /VERSION inside the container was provided to verify the update, with the initial threshold set at 2.0.20261119. Jonathan5 reported confusion when this check returned exactly 2.0.20261119 despite docker images showing 2.0.20261119-0203, and confirming Ruby 4.0.10 and NGINX 1.26.3. david acknowledged the mistake and updated the threshold to “2.0.20261119 or higher”.

Later, peternlewis noted their Discourse dashboard showed version 2026.7.6 (up to date), but cat /VERSION returned 2.0.20260803, with Ruby 3.4.10 installed. supermathie clarified that /VERSION reflects the base image version, not the application version. When peternlewis expressed confusion about the discrepancy between the dashboard and the version check, NateDhaliwal advised performing a ./launcher rebuild app to ensure the base image is updated, aligning with the original instructions.

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

I think you just need to do a ./launcher rebuild app.