Your NGINX server could be running normally and still be vulnerable to a critical security flaw.
On November 18, 2026, researchers disclosed NGINX2ROOT, a group of five vulnerabilities affecting NGINX HTTP/2, HTTP/3, resolver, and mail proxy components. Under certain conditions, these flaws can allow unauthenticated attackers to crash NGINX processes or execute unauthorized code.
Researchers also demonstrated how an NGINX exploit could be combined with a separate Linux kernel vulnerability to gain root access to the server.
NGINX has released security fixes. But for hosting companies managing multiple customer environments, simply knowing that a patch exists isn’t enough.
Which servers are affected? Does your hosting control panel have a patched package? And how do you deploy updates without unnecessarily disrupting customer websites?
This guide explains the five vulnerabilities, affected versions, temporary mitigations, and practical steps hosting operations teams should take to secure their infrastructure.
What Is NGINX2ROOT?
NGINX2ROOT refers to five NGINX vulnerabilities that can enable unauthenticated remote code execution in affected server configurations.
The vulnerabilities involve memory corruption and use-after-free conditions in NGINX components responsible for HTTP connections, DNS resolution, and mail proxy functionality.
NGINX commonly operates as a web server, reverse proxy, or load balancer. For hosting providers, that often places it directly in front of customer websites and applications.
A successful exploit could compromise the NGINX worker process, potentially exposing application traffic or creating an entry point for additional attacks.
The researchers at Xint demonstrated an attack chain involving a separate Linux kernel vulnerability that escalated a compromised worker process to root privileges.
However, exploiting an NGINX vulnerability does not automatically grant root access. The result depends on the worker’s existing permissions and whether a separate privilege-escalation path is available.
For hosting providers, this is a reason to review both NGINX security and the underlying operating system.
Five NGINX2ROOT Vulnerabilities Explained
NGINX2ROOT covers five CVEs that affect different components of NGINX.
| CVE | Component | Vulnerability |
|---|---|---|
| CVE-2026-123007 | HTTP/2 | Memory corruption in HTTP/2 flow control |
| CVE-2026-123633 | HTTP/2 | Use-after-free in HTTP/2 connection handling |
| CVE-2026-123634 | Resolver | Use-after-free during DNS resolver response processing |
| CVE-2026-121810 | HTTP/3 | Use-after-free in HTTP/3 processing |
| CVE-2026-113425 | Mail proxy | Use-after-free in the NGINX mail proxy module |
F5 assigned the five vulnerabilities a CVSS v4.0 score of 9.2 (Critical). The official NGINX security advisory also provides its own component-specific severity classifications.
Why CVE-2026-123007 needs immediate attention
CVE-2026-123007 is particularly important for hosting providers because it affects NGINX HTTP/2 functionality.
HTTP/2 is widely used to serve HTTPS traffic. The vulnerability involves incorrect flow-control handling that can cause memory corruption when an attacker sends specially crafted traffic.
The affected code dates back to NGINX 1.9.5, released in 2015.
An attacker may be able to crash NGINX workers or, under exploitable conditions, achieve remote code execution with worker-process privileges.
The other four CVEs require more specific conditions involving HTTP/2 proxying, DNS resolver activity, HTTP/3, or mail proxy functionality.
The important point for hosting teams is that the NGINX version alone does not determine exposure. Enabled modules, configuration, and vendor patches also matter.
Which NGINX Versions Are Affected?
NGINX released security fixes on November 18, 2026.
| NGINX release | Security status |
|---|---|
| Open Source 1.30.6 | Affected by the disclosed issues where applicable |
| Open Source 1.30.7 | Patched stable release |
| Open Source 1.31.8 | Affected by the disclosed issues where applicable |
| Open Source 1.31.9 | Patched mainline release |
| Older NGINX releases | Check the affected range for each CVE |
| NGINX Plus | Check the relevant F5 security advisory and patched build |
| Linux distribution packages | Verify vendor-specific security fixes and backports |
For CVE-2026-123007, the officially listed vulnerable upstream range extends from NGINX 1.9.5 through 1.31.8, with affected configurations requiring HTTP/2.
Other NGINX2ROOT vulnerabilities have different version ranges.
An older version number does not always mean a Linux distribution package remains vulnerable. Some vendors backport security fixes without replacing the upstream version number.
Administrators should check the full installed package release and compare it with the appropriate vendor advisory.
For further guidance, see SupportPRO’s guide to assessing whether a newly published CVE affects your servers.
Which Hosting Environments Need Attention?
This is where NGINX2ROOT becomes an operational challenge.
Hosting companies rarely manage identical server environments. Different customers may use different Linux distributions, hosting panels, NGINX packages, or container configurations.
A patch procedure that works for one server may not apply to another.
| Hosting environment | What to check | Recommended approach |
|---|---|---|
| NGINX Open Source | Installed version, active modules, HTTP/2 and HTTP/3 settings | Update to a patched release and verify the deployed binary |
| Plesk | sw-nginx, sw-cp-server, and current Plesk security advisory | Follow Plesk-specific package and mitigation instructions |
| cPanel/WHM | Whether NGINX is installed, who manages the package, and which version is deployed | Follow the responsible vendor’s supported update procedure |
| Ubuntu, Debian, and other Linux distributions | Full package release and distribution security advisory | Install vendor-provided fixes, including backported patches |
| Docker and container environments | Image version, digest, and running container version | Redeploy patched images and verify running workloads |
| Reverse proxies and load balancers | Enabled protocols, traffic termination, and backend configuration | Check each NGINX instance separately |
Plesk servers require particular attention
Plesk uses NGINX for customer websites through sw-nginx and for its administration interface through sw-cp-server.
As of the Plesk advisory updated on November 19, 2026, Plesk was preparing an update incorporating NGINX 1.30.7.
Until the applicable release becomes available, administrators should follow Plesk’s official temporary mitigation instructions and verify which components remain exposed.
Plesk also warns that applying its mitigations may briefly interrupt services.
Refer to the official Plesk NGINX2ROOT security advisory for the latest package status.
Do automatic security updates cover NGINX?
Not necessarily.
For example, Laravel Forge notes that its automatic Ubuntu security updates do not update the NGINX packages installed through its separate repositories.
That distinction matters when a hosting operations team assumes automated operating-system updates also cover every web server component.
Verify the source of your NGINX packages rather than assuming they are covered by your existing update schedule.
How to Check Whether Your NGINX Server Is Vulnerable
The following commands help administrators begin an NGINX vulnerability assessment on standard Linux installations.
They are diagnostic checks, not a substitute for vendor-specific package validation.
tep 1: Check the installed NGINX version
nginx -v
nginx -V
The first command displays the NGINX version. The second displays build details, including compiled modules and configuration options.
Check whether the build includes HTTP/2, HTTP/3, or other modules associated with the vulnerabilities.
Step 2: Review the active configuration
sudo nginx -T
This command prints the effective NGINX configuration.
Look for enabled HTTP/2 or HTTP/3, resolver directives, proxy configurations, and mail proxy functionality.
For servers using vendor-managed configurations, avoid manually changing generated files without checking the vendor’s supported procedure.
Step 3: Verify external HTTP/2 exposure
On a server you administer, use an authorized external test to check protocol negotiation:
openssl s_client -connect example.com:443 \
-servername example.com \
-alpn h2,http/1.1 </dev/null
Replace example.com with the relevant hostname.
If the output reports ALPN protocol: h2, that endpoint negotiates HTTP/2.
This does not, by itself, prove that NGINX is vulnerable. It establishes protocol availability at the tested TLS endpoint. You must still identify the terminating server and verify its NGINX build and patch status.
For hosting fleets, repeat the assessment across relevant public-facing endpoints, reverse proxies, and customer infrastructure.
How to Patch NGINX2ROOT Without Unnecessary Customer Downtime
For a hosting operations manager, a successful security update has two outcomes:
The vulnerability is addressed, and customer services continue operating correctly.
A structured maintenance process helps achieve both.
1. Prioritize exposed production servers
Start with internet-facing NGINX servers running vulnerable packages and accepting HTTP/2 connections.
Then investigate servers using HTTP/3, resolver-dependent proxy configurations, or the NGINX mail proxy module.
Prioritize systems according to external exposure, customer impact, patch availability, and whether compensating controls are already active.
Assign a clear owner to each affected server or server group.
2. Confirm the correct patch source
Before upgrading, identify whether NGINX was installed through:
- Official NGINX packages
- A Linux distribution repository
- A hosting control panel
- A custom package repository
- A container image
Use the corresponding vendor’s documented update procedure.
Do not replace panel-managed NGINX binaries with unrelated upstream packages without checking compatibility and support requirements.
3. Prepare the maintenance change
For production hosting environments, review the intended configuration changes, relevant backups, and rollback procedures.
Where infrastructure supports it, stage the update on a representative server before deploying it to the entire fleet.
For load-balanced applications, drain traffic from one server at a time to reduce the chance of customer-facing interruptions.
Schedule or communicate maintenance when the change could affect service availability.
4. Install the security update and validate NGINX
After installing the applicable patched package, test the NGINX configuration:
sudo nginx -t
For a standard systemd-managed NGINX installation, a restart can activate the updated service binary:
sudo systemctl restart nginx
Then check the service:
sudo systemctl status nginx
These commands are examples for standard Linux installations. Hosting control panels and container deployments may require different activation procedures.
5. Verify that customer services still work
A successful NGINX restart does not guarantee that hosted websites and applications are healthy.
After patching, check:
- Customer-facing HTTP and HTTPS responses
- Reverse-proxy and upstream application connectivity
- TLS and protocol negotiation
- Authentication, login, and other critical application paths
- NGINX error logs and unexpected worker crashes
- The actual running NGINX build and vendor patch status
Also confirm that any temporary workaround remains in place until the applicable patch is active and verified.
A remediation ticket should only be closed after the security fix and service-health checks have both passed.
What If You Cannot Patch NGINX Immediately?
If a patched package is unavailable, temporary mitigations may reduce exposure while the team coordinates an upgrade.
For CVE-2026-123007 and CVE-2026-123633, disabling HTTP/2 on affected NGINX listeners can mitigate the HTTP/2 attack paths.
However, that does not resolve vulnerabilities involving HTTP/3, the resolver, or mail proxy functionality.
Administrators may need to disable specific affected features, restrict exposure, or apply other vendor-approved controls.
Review the configuration and customer impact before making changes. For example, disabling HTTP/2 can affect connection behavior and performance, while other mitigation changes may affect applications that depend on those NGINX features.
Temporary mitigations should have an assigned owner and an expiry or review date.
They reduce risk but do not replace permanent security updates.
How Can Hosting Managers Verify NGINX2ROOT Remediation?
The most common operational mistake is treating an installed patch as proof that the problem has been resolved everywhere.
Across a hosting fleet, some servers may still run old binaries, containers may not have been redeployed, or customer-facing endpoints may route traffic through another vulnerable proxy.
A simple remediation record helps operations teams maintain visibility.
| Verification item | Evidence to record |
|---|---|
| Server identification | Hostname, asset ID, and responsible team |
| NGINX package | Version, package release, and source |
| Exposure assessment | Relevant protocols, modules, and configuration |
| Remediation | Patch installed or temporary mitigation applied |
| Service validation | HTTP checks, application health, and logs |
| Final status | Verified, pending, or exception approved |
For a hosting company managing dozens or hundreds of servers, this information makes it easier to identify outstanding security risks and report progress.
It also supports a more consistent vulnerability response process for future disclosures.
For a broader approach to prevention and maintenance, read on how proactive server management prevents expensive IT problems.
NGINX2ROOT Hosting Operations Checklist
Before closing the incident or maintenance ticket, confirm that your team has:
- Identified public-facing and internally deployed NGINX instances.
- Checked installed versions, modules, and affected configurations.
- Verified the appropriate vendor patch or backport.
- Prioritized exposed production systems.
- Applied approved temporary mitigations where necessary.
- Completed patch installation or deployment.
- Verified the running NGINX version and relevant security fix.
- Tested customer websites and critical application paths.
- Reviewed logs for suspicious activity or service errors.
- Documented remediation results and unresolved exceptions.
If you observe signs of compromise, follow your incident-response procedure. Preserve relevant evidence and investigate possible unauthorized activity. Patching alone does not establish that an already compromised system is safe.
Securing Hosting Infrastructure Beyond NGINX2ROOT
NGINX2ROOT shows how vulnerabilities in widely used server components can create operational risks for hosting providers.
Applying the latest NGINX security patch is important. But protecting customer infrastructure also requires accurate asset inventories, regular vulnerability assessments, secure configurations, and consistent monitoring.
For hosting operations teams, the goal is not simply to update individual servers. It is to make sure no affected system is overlooked and that every security change is properly verified.
SupportPRO provides server administration and management services to help hosting companies maintain and secure their infrastructure.
Whether you need routine Linux server management, security patch coordination, or assistance with a critical server issue, our teams can support your infrastructure operations.
Need help assessing NGINX2ROOT exposure across your hosting environment?
Explore SupportPRO’s Emergency Server Support for assistance with server security, patching, and remediation.
Frequently Asked Questions About NGINX2ROOT
What is NGINX2ROOT?
NGINX2ROOT is a group of five vulnerabilities disclosed in November 2026 that affect NGINX HTTP/2, HTTP/3, resolver, and mail proxy functionality. Under specific conditions, attackers may exploit them to execute unauthorized code.
Which NGINX versions fix NGINX2ROOT?
NGINX Open Source 1.30.7 (stable) and 1.31.9 (mainline) contain fixes for the five vulnerabilities. Administrators using vendor-packaged NGINX should verify the relevant security advisory and package release.
Can NGINX2ROOT give attackers root access?
The vulnerabilities can lead to code execution with NGINX worker-process privileges. Researchers demonstrated root access by chaining an NGINX exploit with a separate Linux kernel vulnerability. Root access is not an automatic result of every NGINX exploit.
Does disabling HTTP/2 completely fix NGINX2ROOT?
No. Disabling HTTP/2 mitigates the two HTTP/2 vulnerabilities, CVE-2026-123007 and CVE-2026-123633, on affected listeners. The remaining vulnerabilities require separate assessment and remediation.
Are Plesk and cPanel hosting servers affected?
Plesk has published an advisory covering its NGINX components. cPanel environments need assessment based on whether NGINX is installed, which package is used, and which vulnerable features are enabled. The presence of a hosting control panel alone does not prove exposure.
How should hosting companies prioritize NGINX security updates?
Start with exposed, unpatched production servers, particularly those accepting HTTP/2. Then assess the other affected components, coordinate supported patches, and verify remediation alongside customer service health.
Technical References
- NGINX Official Security Advisories
- Xint Research: NGINX2ROOT Remote Code Execution
- Plesk: NGINX2ROOT Security Advisory
- Laravel Forge: NGINX2ROOT Security Advisory

