nginx on Cloudron and the "NGINX2Root" CVEs (CVE-2026-123007 et al.)
-
nginx.org recently published several advisories that are being referred to as "NGINX2Root":
- CVE-2026-123007 – memory corruption in HTTP/2 flow control (major)
- CVE-2026-113425 – use-after-free in mail proxy module (major)
- CVE-2026-123633 – use-after-free in HTTP/2 (medium)
- CVE-2026-123634 – use-after-free in resolver (medium)
- CVE-2026-121810 – use-after-free in HTTP/3 (medium)
Upstream fixes are in nginx 1.30.7 and 1.31.9.
My Cloudron (10.1.6) runs on Ubuntu 26.04.1 LTS with the distro nginx package 1.28.3-2ubuntu1.12, which is the latest version in resolute-security. The Ubuntu changelog for that package does not mention any of the CVEs above, and the Ubuntu CVE tracker still lists 26.04 as "Vulnerable" for CVE-2026-123007. HTTP/2 is enabled on the Cloudron reverse proxy.
My questions:
- Is the Cloudron team aware of these CVEs, and is there a planned fix (an Ubuntu package update, or a Cloudron release that ships or pins a patched nginx)?
- Does Cloudron's nginx configuration use the mail proxy module or HTTP/3 at all, i.e. are CVE-2026-113425 and CVE-2026-121810 relevant for Cloudron?
- Until a fix is available, is there a recommended mitigation (e.g. disabling HTTP/2) that is supported and won't be overwritten by Cloudron?
References:
Thanks!
-
Alas, yet another serious exploit, this time for NginX, which they've named "nginx2root"
https://xint.io/blog/nginx2root-remote-code-execution
I'm currently wondering whether to simply shut down my Cloudron server until further notice? Or is there a less intrusive mitigation?
Thanks!
-
For now I've halted the Cloudron services, rather than turn of the entire server:
systemctl stop box docker nginxThis seems to stop all the local nginx processes. There don't seem to be any nginx updates for Ubuntu (Noble) yet, and it's still running 1.24.0-2ubuntu7.19, which is I think in the affected range.
-
Hello @wu-lee and @kubernetes
From my quick assessment theSCTPKernel module is needed for the root privilege escalation.
TheSCTPKernel module can be disabled on a Cloudron server and should not cause any issues.I have created a script to disable/enable and check the status:
#!/bin/bash # Block or allow the sctp kernel module (nginx2root LPE mitigation) # https://xint.io/blog/nginx2root-remote-code-execution set -eu conf=/etc/modprobe.d/disable-sctp.conf case "${1:-}" in disable) echo "install sctp /bin/false" > "$conf" echo "install sctp_diag /bin/false" >> "$conf" if modprobe -r sctp_diag sctp 2>/dev/null; then echo "sctp blocked and unloaded" else echo "sctp blocked, but still loaded. Reboot to unload it." fi ;; enable) rm -f "$conf" echo "sctp allowed again (loads on demand)" ;; status) [[ -f "$conf" ]] && echo "blocked: yes" || echo "blocked: no" lsmod | grep -q '^sctp ' && echo "loaded: yes" || echo "loaded: no" ;; *) echo "usage: sudo $0 disable|enable|status" exit 1 ;; esacAfter running this script and disabling the
SCTPKernel module, the server needs to be restarted.This only removes the root step of the attack!
The nginx HTTP/2 bug still allows code execution as the nginx worker until HTTP/2 is turned off or a fixed nginx is installed.I am still looking further into it.
-
Ubuntu will provide the nginx security update. I found https://xint.io/blog/nginx2root-remote-code-execution and https://www.rapid7.com/blog/post/ve-cve-2026-123007-critical-nginx-http-2-integer-underflow-leads-to-rce-fixed/ quite informative. From the latter article, "Leveraging CVE-2026-123007 for RCE requires a significant amount of network traffic to be transmitted, approximately 128 GB of HTTP/2 data. Both available network bandwidth and connection timeouts will place practical limitations on Internet exploitation"
If you are worried, you can turn off http2:
find /etc/nginx/applications -type f -name "*.conf" -exec sed -i 's/http2 on/http2 off/g' {} + systemctl restart nginx -
Hello @wu-lee and @kubernetes
From my quick assessment theSCTPKernel module is needed for the root privilege escalation.
TheSCTPKernel module can be disabled on a Cloudron server and should not cause any issues.I have created a script to disable/enable and check the status:
#!/bin/bash # Block or allow the sctp kernel module (nginx2root LPE mitigation) # https://xint.io/blog/nginx2root-remote-code-execution set -eu conf=/etc/modprobe.d/disable-sctp.conf case "${1:-}" in disable) echo "install sctp /bin/false" > "$conf" echo "install sctp_diag /bin/false" >> "$conf" if modprobe -r sctp_diag sctp 2>/dev/null; then echo "sctp blocked and unloaded" else echo "sctp blocked, but still loaded. Reboot to unload it." fi ;; enable) rm -f "$conf" echo "sctp allowed again (loads on demand)" ;; status) [[ -f "$conf" ]] && echo "blocked: yes" || echo "blocked: no" lsmod | grep -q '^sctp ' && echo "loaded: yes" || echo "loaded: no" ;; *) echo "usage: sudo $0 disable|enable|status" exit 1 ;; esacAfter running this script and disabling the
SCTPKernel module, the server needs to be restarted.This only removes the root step of the attack!
The nginx HTTP/2 bug still allows code execution as the nginx worker until HTTP/2 is turned off or a fixed nginx is installed.I am still looking further into it.
-
Gave my AI this thread to deal with things, and it me asked to post this (seems I work for my AI now):
Notes from mitigating 3 Cloudron 10.1.6 / Ubuntu 26.04 servers, in case they help:
- The sed for http2 on isn't enough on its own. Some app configs (here: Collabora, Woodpecker, a Matrix admin UI) use the older listen 443 ssl http2; form. I believe that keeps HTTP/2 on for every site on that port. Check with: grep -rlE 'listen .http2' /etc/nginx/applications. To strip it: sed -i -E '/^\slisten\s/ s/\s+http2(\s*;|\s)/\1/'.
- Cloudron rewrites these configs. About 2 minutes after a reboot, some regenerated configs had http2 on again (I saw HTTP/2 200 from outside). App reconfigures and certificate renewals probably do the same. I run a small script from /etc/cron.d every 2 minutes. It reapplies both edits only when needed, backs up /etc/nginx, runs nginx -t (and rolls back if it fails), then reloads.
- Check from outside rather than trusting the files: curl -sI --http2 --resolve your.domain:443:SERVER_IP https://your.domain/ | head -1 should show HTTP/1.1.
- SCTP is in use on Cloudron: the built-in TURN service (turn container, coturn) had many kernel SCTP sockets open, so modprobe -r can't unload it until a reboot. After blocking it and rebooting, TURN came back with its normal UDP/TCP listeners and no SCTP errors, so the block looks safe. Check your call/WebRTC apps afterwards.
- Other advisories: the stock configs have no mail {} block, no quic/http3 and no resolver. So only the two HTTP/2 bugs (CVE-2026-123007 and -123633) seem relevant to Cloudron's reverse proxy.
- Reboots stop hand-made containers: containers you started yourself with docker run and no restart policy won't come back after the reboot.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login