NGINX2Root (CVE-2026-123007 and CVE-2026-123633): What Happened and Why MioriticHost Servers Are Already Patched
The Short Version: What Happened and Where Things Stand
On November 18, 2026, F5 — the company that maintains nginx — published an out-of-cycle security update addressing 10 vulnerabilities. Two of them are critical and have been collectively named NGINX2Root: CVE-2026-123007 and CVE-2026-123633. MioriticHost hosting servers use nginx with HTTP/2 enabled, which placed them in the affected category until the patch was applied. The automated nightly update installed the fixed package on November 19, 2026 at 04:12 Romanian time, with nginx restarted at 04:14. On November 20 we manually confirmed that the nginx process actually running in memory reports version 1.31.9. Shared hosting customers do not need to take any action. VPS customers who manage their own nginx installation should update — details below.
What the NGINX2Root Vulnerabilities Actually Are
- Nature of the flaws: CVE-2026-123007 and CVE-2026-123633 are memory corruption bugs in nginx's HTTP/2 implementation. A remote, unauthenticated attacker can exploit them to execute arbitrary code with the privileges of the nginx worker process.
- Severity scores: F5 assigned a CVSS 4.0 score of 9.2; CERT-EU rates them at 8.1. The difference comes from the scoring method; either way this is a serious flaw that needs patching quickly.
- Why the name NGINX2Root: When chained with a separate Linux kernel flaw in the SCTP protocol — which had no CVE assigned as of November 19 — the exploit chain could theoretically escalate to root-level access. Security media adopted the NGINX2Root label to describe this full attack path.
- Public exploit: Rapid7 published a technical write-up and a public proof-of-concept for CVE-2026-123007 on November 18. CERT-EU reported no known exploitation in the wild at the time of disclosure, but recommended prioritising the update for internet-facing servers.
- Fixed versions: nginx 1.30.7 (stable branch) and nginx 1.31.9 (mainline branch), both released on November 18, 2026. The recommended interim mitigation for systems that cannot update immediately is to disable HTTP/2.
Why This Affected Us Too — and What We Did About It
On MioriticHost hosting servers, nginx sits in front of Apache and handles all incoming visitor connections. HTTP/2 is enabled for every hosted site. That means our servers were in the affected category before the patch was applied — and we want to be straightforward about that.
Here is the timeline of what happened:
- November 18, 2026: F5 publishes the security update. CloudLinux — the distribution our servers run with cPanel — prepares the patched nginx 1.31.9 package, flagged as urgent.
- November 19, 2026, 04:12 Romanian time: The automated nightly update installs the patched package. Nginx is restarted at 04:14, with no manual intervention.
- November 20, 2026: We manually verify that the nginx process running in memory — not just the installed package — reports version 1.31.9. An updated package is not enough if the old process is still running; we confirmed it is not. On the same day we also performed a full Apache restart so that its worker processes would load any updated system libraries. This is unrelated to the nginx vulnerability itself; it is a hygiene measure, and the restart took a few seconds.
We also reviewed nginx and kernel logs for the window between the vulnerability disclosure and the moment the patch was applied. We found no signs of exploitation — in particular, no abnormal crashes of nginx worker processes, which would be a typical indicator of memory corruption exploit attempts. We are not claiming exploitation was impossible during that window; we are saying we found no evidence that it occurred.
Regarding the root escalation chain: the SCTP module is not loaded and is not present in the kernel on our hosting servers. Additionally, nginx worker processes run under an unprivileged user account, which further limits the potential impact of any worker-level compromise.
What Customers Need to Do
- Shared hosting customers: Nothing. Your sites, cPanel settings, and configurations are unchanged. The patch was applied at the server level and requires no action on your part.
- VPS customers managing their own nginx: You need to update nginx to version 1.30.7 (stable branch) or 1.31.9 (mainline branch) — or to the patched package provided by your Linux distribution — and restart the nginx service after updating. You can check your current version by running nginx -v in a terminal. If updating is not immediately possible, disable HTTP/2 as a temporary measure. The MioriticHost support team can assist on request; open a ticket from the client area at mioritichost.com.
- A note on PHP: A separate PHP security update was also released on November 19, 2026. We are covering that in a dedicated blog post.
Closing Notes
NGINX2Root is a serious set of vulnerabilities with a public exploit available from day one. The exposure window for MioriticHost servers was less than a day — from the disclosure to the automated patch applied in the early hours of the following morning. We found no evidence of exploitation during that interval. Servers are now running nginx 1.31.9 with the running process confirmed updated. Shared hosting customers have no action to take. VPS customers who manage their own nginx should update if they have not done so already.
Category: Hosting






