# Ruby2Shell and Nginx2Root response

**URL:** <https://meta.discourse.org/t/ruby2shell-and-nginx2root-response/417832>\
**Category:** Announcements\
**Created:** [November 19, 2026, 11:52am UTC](https://meta.discourse.org/t/ruby2shell-and-nginx2root-response/417832 "2026-11-19T11:52:19Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)\
**Post date:** [November 19, 2026, 11:52am UTC](https://meta.discourse.org/t/ruby2shell-and-nginx2root-response/417832/1 "2026-11-19T11:52:19Z")

</div>

Critical vulnerabilities have been disclosed this week in [NGINX](https://xint.io/blog/nginx2root-remote-code-execution) and [Ruby](https://verialabs.com/ruby2shell/).

**If you use our managed [discourse.org](http://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](https://meta.discourse.org/t/142537?silent=true), 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:
> 
> ```plaintext
> ./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](https://www.ruby-lang.org/en/news/2026/11/18/multiple-vulnerabilities-in-regexp-and-string/)): 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](https://nginx.org/en/security_advisories.html)): CVE-2026-123007, CVE-2026-123633, CVE-2026-123634, CVE-2026-121810, CVE-2026-113425, CVE-2026-118899, CVE-2026-123640, CVE-2026-125283.

---

<div class="post-metadata">

**Author:** ![Jonathan5](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jonathan5/32/197134_2.png) [@Jonathan5](https://meta.discourse.org/u/Jonathan5)\
**Post date:** [November 19, 2026, 12:30pm UTC](https://meta.discourse.org/t/ruby2shell-and-nginx2root-response/417832/4 "2026-11-19T12:30:30Z")

</div>

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`

---

<div class="post-metadata">

**Author:** ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)\
**Post date:** [November 19, 2026, 12:35pm UTC](https://meta.discourse.org/t/ruby2shell-and-nginx2root-response/417832/5 "2026-11-19T12:35:58Z")

</div>

> [@Jonathan5](#):
>
> After rebuild that command showed exactly 2.0.20261119, which initially confused me

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

> [@david](#):
>
> If the image version is `2.0.20261119` or higher
