-
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.
-
Sorry to disturb you with another vulnerability, but now Nginx is affected. Based on @girish answer here: https://forum.cloudron.io/post/132847 I assume that the 3 first vulnerabilities are not impacting Cloudron but maybe the other 2?
Thanks in advance for your advice!
https://cert.europa.eu/publications/security-advisories/2026-022/
-
https://forum.cloudron.io/topic/16310/nginx-on-cloudron-and-the-nginx2root-cves-cve-2026-123007-et-al. Why not use this thread?
-
N necrevistonnezr referenced this topic
-
https://forum.cloudron.io/topic/16310/nginx-on-cloudron-and-the-nginx2root-cves-cve-2026-123007-et-al. Why not use this thread?
@necrevistonnezr sorry I didn't find it on first search... my bad
-
Hello the fixed Ubuntu packages are already out details here: https://ubuntu.com/security/CVE-2026-123007
As main nginx runs on the cloudron host unattended-upgrades will install those when it runs (or you can do manually)
Note that this is only about the fixed to nginx
That sctp linux kernel rce topic is apart and afaik unfixed
And i've seen no cve to track (probably this https://lore.kernel.org/all/20261110224233.82977-1-yves.bieri@theori.io/) -
-
I think that might be less critical as those 'internal inside container nginx' have a much more narrow usage.
Looking at the 5 CVE description from the xint post:
a.) 3 are related to HTTP/2 or HTTP/3
b.) the other two related to nginx doing proxying (one even more narrow for mail)Topic a.) should be out of scope for internal nginx (as its only about receiving connection on localhost from the 'outside nginx' without https or http/2
Topic b.) would need a bit more checking (i.e. internal collabora nginx does proxying) if that cve could apply here or not@wu-lee just me trying to answer your question for myself + sharing what is my first impression.
-
J james moved this topic from Support
-
Our servers already got the update. you can run
apt-get update && unattended-upgrade(as root) manually on the server as well.root@my:~# apt-cache policy nginx-full nginx-full: Installed: 1.28.3-2ubuntu1.13 Candidate: 1.28.3-2ubuntu1.13 Version table: *** 1.28.3-2ubuntu1.13 500 500 http://de.archive.ubuntu.com/ubuntu resolute-updates/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu resolute-security/universe amd64 Packages 100 /var/lib/dpkg/status 1.28.3-2ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu resolute/universe amd64 Packages -
Our servers already got the update. you can run
apt-get update && unattended-upgrade(as root) manually on the server as well.root@my:~# apt-cache policy nginx-full nginx-full: Installed: 1.28.3-2ubuntu1.13 Candidate: 1.28.3-2ubuntu1.13 Version table: *** 1.28.3-2ubuntu1.13 500 500 http://de.archive.ubuntu.com/ubuntu resolute-updates/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu resolute-security/universe amd64 Packages 100 /var/lib/dpkg/status 1.28.3-2ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu resolute/universe amd64 Packages -
1.24.0-2ubuntu7.20
Me too. Those are recent updates though, and it looks like they include patches for nginx2root:
https://launchpad.net/ubuntu/+source/nginx/1.24.0-2ubuntu7.20
-
J joseph has marked this topic as solved
-
Do we also need to be concerned about Cloudron apps' use of NginX? From the outside it isn't easy to tell which apps use it, and I seem to remember reading that the exploit can also succeed through a reverse proxy.
Hello @wu-lee
Do we also need to be concerned about Cloudron apps' use of NginX?
I can now answer this.
Please check out https://forum.cloudron.io/topic/16322/python-3.12-base-image-scout-findings-and-mitigation-guidance/2 it explains that Cloudron apps can't be effected by this CVE.
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