The discussion addresses the Ruby2Shell vulnerability (GHSA-34m4-m9fh-gqp5) in the context of self-hosting Discourse. AquaL1te initially expressed concern about the security issue and the need for a patch, but quickly confirmed that the latest release (2026.11.x) included the fix with Ruby 4.0.10. However, osmith noted that the ESR release (2026.7) still contained the vulnerable Ruby 4.0.9 when pulling the discourse/discourse:2026.7.5 Docker image.
david clarified that the ESR release typically shares the same Docker image as latest when using the standard install method, and advised that the discourse/discourse image is experimental and not recommended for production. osmith confirmed they were using the experimental image via docker-compose. david stated he would update the experimental image, and later confirmed that discourse/discourse:2026.7.5 was successfully updated to include Ruby 4.0.10. David also shared a link to a meta topic detailing the response to both this and a related Nginx vulnerability.
The ESR release uses the same docker image as latest, so a ./launcher rebuild app should bring in the new ruby version. Are you seeing something different?
We use the discourse/discourse:2026.7.5 image in docker-compose.yml and fetching it results in an image that still has ruby 4.0.9. Do you recommend using a different image instead?
discourse/discourse is experimental, and not really recommended for production use. Currently, the only supported install path is the ‘standard install’.
That said, I will see if we can get the experimental discourse/discourse image upgraded, and report back here