-
AutorBeiträge
-
-
19. November 2026 um 11:07 Uhr - Views: 29 #45787
Critical security patch for nginx
Last night a chain of critical security issues for nginx was disclosed: https://nginx2root.com/
nginx has released fixed images and we have updated our nginx images with those as bases.
If you are using Docker, make sure to switch to those updated images. For most systems this can be achieved by running the commands below.If you are currently using an OTOBO 11.1 beta version and/or if you have configured a specific nginx version in your .env-file, you have to explicitly switch to the latest nginx version of your respective branch (latest-10_1, latest-11_0 or latest-11_1), or the versions rel-10_1_18, rel-11_0_16 or rel-11_1_1 before that in the .env-file.
(The exact nginx patch level version does not have to match your OTOBO version.)Otobo Docker
cd /opt/otobo-docker
docker compose pull nginx
docker compose down nginx && docker compose up nginx -dAfter pulling and restarting the containers you can check the nginx version by running:
docker compose exec nginx nginx -vIt must return:
nginx version: nginx/1.31.9This update does not require OTOBO to be updated at the same time.
Otobo Podman
machinectl shell otobo@
podman images
podman pull docker.io/rotheross/otobo-nginx-webproxy:rel-11_1_1
systemctl --user restart otobo.targetAfter pulling and restarting the containers you can check the nginx version by running:
podman exec otobo-nginx nginx -vIt must return:
nginx version: nginx/1.31.9Heads up: Elasticsearch
We are also waiting for an also critical security release for Elasticsearch which is affected by Java4Shell (CVE-2026-114938).
We’ll send a second security notice once Elastic has supplied a fixed image. In our Docker environment Elasticsearch is not directly accessible from the outside, but could, in the meantime, also be deactivated by disabling the Elasticsearch webservice in OTOBO and stopping the container. If that is done keep in mind to reindex Elasticsearch after restarting it.
For native installations please check whether you are affected by either and update from the OS repositories as applicable.
-
-
AutorBeiträge
- Du musst angemeldet sein, um auf dieses Thema antworten zu können.
