NGINX2Root: your host should handle the patching
A critical NGINX vulnerability should not turn into an evening of server maintenance for your developers. Intercube has already applied the security updates across the entire fleet. Keeping the web server maintained is part of the managed hosting service our customers receive.
- Author
- Intercube
- Published
- Reading time
- 4 min read
01
The web server needs its own maintenance
NGINX receives visitors before a request reaches the application. It can handle HTTPS, serve files and route traffic to an application or API. A flaw here can expose a website even when its application code is fully up to date.
Xint disclosed five NGINX vulnerabilities in its NGINX2Root research. They affect HTTP/2, HTTP/3, the resolver and mail proxy configurations. Successful exploitation can allow an unauthenticated attacker to run code with the permissions of an NGINX worker. Xint demonstrated a further escalation to host root through a separate Linux kernel flaw.
- CVE-2026-123007 and CVE-2026-123633 affect HTTP/2 processing.
- CVE-2026-121810 affects HTTP/3 processing.
- CVE-2026-123634 affects particular resolver configurations.
- CVE-2026-113425 affects the mail proxy.
02
Security releases are available
NGINX released stable version 1.30.7 and mainline version 1.31.9 on 18 November 2026. The release notes include the five NGINX2Root fixes alongside other security corrections. For the HTTP/2 flaws, an affected server must have HTTP/2 enabled. The other issues depend on the relevant module and configuration. Wiz traces CVE-2026-123007 back to version 1.9.5 and CVE-2026-123633 to 1.19.7.
The update needs to reach the running service. A package installed on disk is only part of that work. The new binary must be loaded through a restart or a supported live binary upgrade. A normal configuration reload does not replace it. Distribution packages can contain backported fixes, so compare the complete package release with the supplier’s advisory.
03
This NGINX update is already taken care of
Intercube has completed the NGINX update across the entire fleet. Our engineers handled the web-server patching as part of the managed hosting service, so customers do not have to arrange that work for this release.
That responsibility continues after an urgent advisory. Intercube operates the web server and managed runtimes, maintains the agreed infrastructure configuration and provides engineering support from people who know the environment. When a release affects the way an application connects to that infrastructure, your developers have a technical team to work with.
04
Choose hosting that includes the maintenance
If a security notice leaves your developers searching for server access and deciding who will install the fix, review who owns the hosting maintenance. Intercube managed hosting puts that work with engineers who operate the environment behind your website.
We can prepare the destination infrastructure and work with your developers on a staging or preview environment to validate the application before switching traffic. Migration to Intercube managed hosting is included at no additional cost. Bring us your current hosting setup and we will plan the transfer and ongoing infrastructure ownership with you.
What this means for your hosting
- NGINX2Root covers five vulnerabilities in the web server and related modules.
- NGINX 1.30.7 and 1.31.9 contain the upstream fixes.
- The running service must use the patched binary.
- Intercube has already updated NGINX across its entire fleet.
- Migration to Intercube managed hosting is included at no additional cost.