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.