<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[nginx on Cloudron and the "NGINX2Root" CVEs (CVE-2026-123007 et al.)]]></title><description><![CDATA[<p dir="auto"><a href="http://nginx.org" target="_blank" rel="noopener noreferrer nofollow ugc">nginx.org</a> recently published several advisories that are being referred to as "NGINX2Root":</p>
<ul>
<li>CVE-2026-123007 – memory corruption in HTTP/2 flow control (major)</li>
<li>CVE-2026-113425 – use-after-free in mail proxy module (major)</li>
<li>CVE-2026-123633 – use-after-free in HTTP/2 (medium)</li>
<li>CVE-2026-123634 – use-after-free in resolver (medium)</li>
<li>CVE-2026-121810 – use-after-free in HTTP/3 (medium)</li>
</ul>
<p dir="auto">Upstream fixes are in nginx 1.30.7 and 1.31.9.</p>
<p dir="auto">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.</p>
<p dir="auto">My questions:</p>
<ol>
<li>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)?</li>
<li>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?</li>
<li>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?</li>
</ol>
<p dir="auto">References:</p>
<ul>
<li><a href="https://nginx.org/en/security_advisories.html" target="_blank" rel="noopener noreferrer nofollow ugc">https://nginx.org/en/security_advisories.html</a></li>
<li><a href="https://ubuntu.com/security/CVE-2026-123007" target="_blank" rel="noopener noreferrer nofollow ugc">https://ubuntu.com/security/CVE-2026-123007</a></li>
</ul>
<p dir="auto">Thanks!</p>
]]></description><link>https://forum.cloudron.io/topic/16310/nginx-on-cloudron-and-the-nginx2root-cves-cve-2026-123007-et-al.</link><generator>RSS for Node</generator><lastBuildDate>Thu, 19 Nov 2026 02:31:29 GMT</lastBuildDate><atom:link href="https://forum.cloudron.io/topic/16310.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 18 Nov 2026 18:08:30 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to nginx on Cloudron and the "NGINX2Root" CVEs (CVE-2026-123007 et al.) on Wed, 18 Nov 2026 23:10:19 GMT]]></title><description><![CDATA[<p dir="auto">Gave my AI this thread to deal with things, and it me asked to post this (seems I work for my AI now):</p>
<blockquote>
<p dir="auto">Notes from mitigating 3 Cloudron 10.1.6 / Ubuntu 26.04 servers, in case they help:</p>
<ol>
<li>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 .<em>http2' /etc/nginx/applications. To strip it: sed -i -E '/^\s</em>listen\s/ s/\s+http2(\s*;|\s)/\1/'.</li>
<li>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.</li>
<li>Check from outside rather than trusting the files: curl -sI --http2 --resolve your.domain:443:SERVER_IP <a href="https://your.domain/" target="_blank" rel="noopener noreferrer nofollow ugc">https://your.domain/</a> | head -1 should show HTTP/1.1.</li>
<li>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.</li>
<li>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.</li>
<li>Reboots stop hand-made containers: containers you started yourself with docker run and no restart policy won't come back after the reboot.</li>
</ol>
</blockquote>
]]></description><link>https://forum.cloudron.io/post/133062</link><guid isPermaLink="true">https://forum.cloudron.io/post/133062</guid><dc:creator><![CDATA[marcusquinn]]></dc:creator><pubDate>Wed, 18 Nov 2026 23:10:19 GMT</pubDate></item><item><title><![CDATA[Reply to nginx on Cloudron and the "NGINX2Root" CVEs (CVE-2026-123007 et al.) on Wed, 18 Nov 2026 20:44:39 GMT]]></title><description><![CDATA[<blockquote>
<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/james" aria-label="Profile: james">@<bdi>james</bdi></a> <a href="/post/133053">said</a>:<br />
The <code>SCTP</code> Kernel module can be disabled on a Cloudron server and should not cause any issues.</p>
</blockquote>
<p dir="auto">Thanks for the script! On my (home) server, it wasn’t even enabled</p>
]]></description><link>https://forum.cloudron.io/post/133057</link><guid isPermaLink="true">https://forum.cloudron.io/post/133057</guid><dc:creator><![CDATA[necrevistonnezr]]></dc:creator><pubDate>Wed, 18 Nov 2026 20:44:39 GMT</pubDate></item><item><title><![CDATA[Reply to nginx on Cloudron and the "NGINX2Root" CVEs (CVE-2026-123007 et al.) on Wed, 18 Nov 2026 19:48:09 GMT]]></title><description><![CDATA[<p dir="auto">Ubuntu will provide the nginx security update. I found <a href="https://xint.io/blog/nginx2root-remote-code-execution" target="_blank" rel="noopener noreferrer nofollow ugc">https://xint.io/blog/nginx2root-remote-code-execution</a> and <a href="https://www.rapid7.com/blog/post/ve-cve-2026-123007-critical-nginx-http-2-integer-underflow-leads-to-rce-fixed/" target="_blank" rel="noopener noreferrer nofollow ugc">https://www.rapid7.com/blog/post/ve-cve-2026-123007-critical-nginx-http-2-integer-underflow-leads-to-rce-fixed/</a> 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"</p>
<p dir="auto">If you are worried, you can turn off http2:</p>
<pre><code>find /etc/nginx/applications -type f -name "*.conf" -exec sed -i 's/http2 on/http2 off/g' {} +
systemctl restart nginx
</code></pre>
]]></description><link>https://forum.cloudron.io/post/133056</link><guid isPermaLink="true">https://forum.cloudron.io/post/133056</guid><dc:creator><![CDATA[girish]]></dc:creator><pubDate>Wed, 18 Nov 2026 19:48:09 GMT</pubDate></item><item><title><![CDATA[Reply to nginx on Cloudron and the "NGINX2Root" CVEs (CVE-2026-123007 et al.) on Wed, 18 Nov 2026 19:36:23 GMT]]></title><description><![CDATA[<p dir="auto">Hello <a class="plugin-mentions-user plugin-mentions-a" href="/user/wu-lee" aria-label="Profile: wu-lee">@<bdi>wu-lee</bdi></a> and <a class="plugin-mentions-user plugin-mentions-a" href="/user/kubernetes" aria-label="Profile: kubernetes">@<bdi>kubernetes</bdi></a><br />
From my quick assessment the <code>SCTP</code> Kernel module is needed for the root privilege escalation.<br />
The <code>SCTP</code> Kernel module can be disabled on a Cloudron server and should not cause any issues.</p>
<p dir="auto">I have created a script to disable/enable and check the status:</p>
<pre><code class="language-bash">#!/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" &gt; "$conf"
    echo "install sctp_diag /bin/false" &gt;&gt; "$conf"
    if modprobe -r sctp_diag sctp 2&gt;/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" ]] &amp;&amp; echo "blocked: yes" || echo "blocked: no"
    lsmod | grep -q '^sctp ' &amp;&amp; echo "loaded: yes" || echo "loaded: no"
    ;;
*)
    echo "usage: sudo $0 disable|enable|status"
    exit 1
    ;;
esac
</code></pre>
<p dir="auto">After running this script and disabling the <code>SCTP</code> Kernel module, the server needs to be restarted.</p>
<p dir="auto">This only removes the root step of the attack!<br />
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.</p>
<p dir="auto">I am still looking further into it.</p>
]]></description><link>https://forum.cloudron.io/post/133053</link><guid isPermaLink="true">https://forum.cloudron.io/post/133053</guid><dc:creator><![CDATA[james]]></dc:creator><pubDate>Wed, 18 Nov 2026 19:36:23 GMT</pubDate></item><item><title><![CDATA[Reply to nginx on Cloudron and the "NGINX2Root" CVEs (CVE-2026-123007 et al.) on Wed, 18 Nov 2026 18:44:44 GMT]]></title><description><![CDATA[<p dir="auto">For now I've halted the Cloudron services, rather than turn of the entire server:</p>
<pre><code>systemctl stop box docker nginx
</code></pre>
<p dir="auto">This 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.</p>
]]></description><link>https://forum.cloudron.io/post/133050</link><guid isPermaLink="true">https://forum.cloudron.io/post/133050</guid><dc:creator><![CDATA[wu-lee]]></dc:creator><pubDate>Wed, 18 Nov 2026 18:44:44 GMT</pubDate></item><item><title><![CDATA[Reply to nginx on Cloudron and the "NGINX2Root" CVEs (CVE-2026-123007 et al.) on Wed, 18 Nov 2026 18:09:36 GMT]]></title><description><![CDATA[<p dir="auto">Alas, yet another serious exploit, this time for NginX, which they've named "nginx2root"</p>
<p dir="auto"><a href="https://nginx2root.com/" target="_blank" rel="noopener noreferrer nofollow ugc">https://nginx2root.com/</a></p>
<p dir="auto"><a href="https://xint.io/blog/nginx2root-remote-code-execution" target="_blank" rel="noopener noreferrer nofollow ugc">https://xint.io/blog/nginx2root-remote-code-execution</a></p>
<p dir="auto">I'm currently wondering whether to simply shut down my Cloudron server until further notice? Or is there a less intrusive mitigation?</p>
<p dir="auto">Thanks!</p>
]]></description><link>https://forum.cloudron.io/post/133046</link><guid isPermaLink="true">https://forum.cloudron.io/post/133046</guid><dc:creator><![CDATA[wu-lee]]></dc:creator><pubDate>Wed, 18 Nov 2026 18:09:36 GMT</pubDate></item></channel></rss>