Hi,
in what capacity is nextcloud aio impacted by nginx2root (https://nginx2root.com/) and is there a timeline for a container update if it is affected?
Thx,
Dark-Sider
Hi,
in what capacity is nextcloud aio impacted by nginx2root (https://nginx2root.com/) and is there a timeline for a container update if it is affected?
Thx,
Dark-Sider
I would say it shouldn’t be affected because AIO doesn’t use NGINX. However, there might be an NGINX instance running inside the Nextcloud Talk container if you’re using that. But as far as I know, the vulnerability can only be exploited via HTTP/2 requests and, in the default configuration at least, everything in AIO runs behind a Caddy reverse proxy that terminates HTTP/2. So you should still be fine.
If you’re running community containers such as NGINX Proxy Manager, or a separate NGINX proxy in front of AIO, though, you should patch them as soon as possible. They may be affected, and the vulnerability could be exploited, especially if they’re directly exposed to the internet.
For all using nginx:
root@DebianServerVM2:~# grep " upgrade " /var/log/dpkg.log | tail -n 1
2026-11-19 07:54:16 upgrade nginx:amd64 1.31.8-1~trixie 1.31.9-1~trixie
root@DebianServerVM2:~#
The Patch is available
nginx -v
nginx version: nginx/1.31.9