Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Offical apps | Community apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Security
  3. nginx on Cloudron and the "NGINX2Root" CVEs (CVE-2026-123007 et al.)

nginx on Cloudron and the "NGINX2Root" CVEs (CVE-2026-123007 et al.)

Scheduled Pinned Locked Moved Solved Security
nginxsecurity
17 Posts 10 Posters 600 Views 12 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • jamesJ
    jamesJ
    james
    Staff
    wrote last edited by james
    #4

    Hello @wu-lee and @kubernetes
    From my quick assessment the SCTP Kernel module is needed for the root privilege escalation.
    The SCTP Kernel 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
        ;;
    esac
    

    After running this script and disabling the SCTP Kernel 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.

    necrevistonnezrN 1 Reply Last reply
    3
    • girishG
      girishG
      girish
      Staff
      wrote last edited by girish
      #5

      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
      
      1 Reply Last reply
      3
      • jamesJ james

        Hello @wu-lee and @kubernetes
        From my quick assessment the SCTP Kernel module is needed for the root privilege escalation.
        The SCTP Kernel 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
            ;;
        esac
        

        After running this script and disabling the SCTP Kernel 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.

        necrevistonnezrN
        necrevistonnezrN
        necrevistonnezr
        Super Fan
        wrote last edited by
        #6

        @james said:
        The SCTP Kernel module can be disabled on a Cloudron server and should not cause any issues.

        Thanks for the script! On my (home) server, it wasn’t even enabled

        marcusquinnM 1 Reply Last reply
        1
        • necrevistonnezrN necrevistonnezr

          @james said:
          The SCTP Kernel module can be disabled on a Cloudron server and should not cause any issues.

          Thanks for the script! On my (home) server, it wasn’t even enabled

          marcusquinnM
          marcusquinnM
          marcusquinn
          CA Maintainer Super Fan
          wrote last edited by
          #7

          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:

          1. 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/'.
          2. 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.
          3. 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.
          4. 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.
          5. 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.
          6. Reboots stop hand-made containers: containers you started yourself with docker run and no restart policy won't come back after the reboot.

          Web Design & Development: https://www.evergreen.je
          Technology & Apps: https://www.marcusquinn.com

          1 Reply Last reply
          0
          • G
            G
            giofonseca
            wrote last edited by
            #8

            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/

            1 Reply Last reply
            1
            • necrevistonnezrN
              necrevistonnezrN
              necrevistonnezr
              Super Fan
              wrote last edited by
              #9

              https://forum.cloudron.io/topic/16310/nginx-on-cloudron-and-the-nginx2root-cves-cve-2026-123007-et-al. Why not use this thread?

              G 1 Reply Last reply
              2
              • necrevistonnezrN necrevistonnezr referenced this topic
              • necrevistonnezrN necrevistonnezr

                https://forum.cloudron.io/topic/16310/nginx-on-cloudron-and-the-nginx2root-cves-cve-2026-123007-et-al. Why not use this thread?

                G
                G
                giofonseca
                wrote last edited by
                #10

                @necrevistonnezr sorry I didn't find it on first search... my bad

                1 Reply Last reply
                1
                • H
                  H
                  huehner
                  wrote last edited by
                  #11

                  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/)

                  1 Reply Last reply
                  1
                  • W
                    W
                    wu-lee
                    wrote last edited by
                    #12

                    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.

                    jamesJ 1 Reply Last reply
                    0
                    • H
                      H
                      huehner
                      wrote last edited by
                      #13

                      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.

                      1 Reply Last reply
                      0
                      • jamesJ james moved this topic from Support
                      • J
                        J
                        joseph
                        Staff
                        wrote last edited by
                        #14

                        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
                        
                        jdaviescoatesJ 1 Reply Last reply
                        3
                        • J joseph

                          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
                          
                          jdaviescoatesJ
                          jdaviescoatesJ
                          jdaviescoates
                          Super Fan
                          wrote last edited by jdaviescoates
                          #15

                          @joseph said:

                          nginx-full:
                          Installed: 1.28.3-2ubuntu1.13
                          Candidate: 1.28.3-2ubuntu1.13

                          My servers are still on 24.04. I've got:

                          nginx-full:
                          Installed: 1.24.0-2ubuntu7.20
                          Candidate: 1.24.0-2ubuntu7.20

                          I use Cloudron with Gandi & Hetzner

                          W 1 Reply Last reply
                          2
                          • jdaviescoatesJ jdaviescoates

                            @joseph said:

                            nginx-full:
                            Installed: 1.28.3-2ubuntu1.13
                            Candidate: 1.28.3-2ubuntu1.13

                            My servers are still on 24.04. I've got:

                            nginx-full:
                            Installed: 1.24.0-2ubuntu7.20
                            Candidate: 1.24.0-2ubuntu7.20

                            W
                            W
                            wu-lee
                            wrote last edited by wu-lee
                            #16

                            @jdaviescoates said:

                            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

                            1 Reply Last reply
                            1
                            • J joseph has marked this topic as solved
                            • W wu-lee

                              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.

                              jamesJ
                              jamesJ
                              james
                              Staff
                              wrote last edited by james
                              #17

                              Hello @wu-lee

                              @wu-lee said:

                              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.

                              1 Reply Last reply
                              1

                              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
                              Reply
                              • Reply as topic
                              Log in to reply
                              • Oldest to Newest
                              • Newest to Oldest
                              • Most Votes


                              • Login

                              • Don't have an account? Register

                              • Login or register to search.
                              • First post
                                Last post
                              0
                              • Categories
                              • Recent
                              • Tags
                              • Popular
                              • Bookmarks
                              • Search