All reports

NGINX2Root: Critical NGINX vulnerabilities — emergency security patching and customer action required

WAYSCLOUD-TR-2026-0030Security ReportcriticalAction Taken
Published: 2026-11-19 09:35:00 UTC
Event: Nov 18, 2026

Summary

On 18 November 2026, F5 disclosed multiple serious security vulnerabilities in NGINX, one of the world's most widely deployed web servers, reverse proxies and traffic management components.

Five of these vulnerabilities, collectively referred to by security researchers as NGINX2Root, could potentially allow unauthenticated attackers to execute arbitrary code within the security context of an affected NGINX worker process. The vulnerabilities carry CVSS v4.0 scores of 9.2 (Critical) and CVSS v3.1 scores of 8.1 (High).

WAYSCloud initiated immediate security patching across its own services and infrastructure nodes, Shared Hosting environments, and customer services covered by applicable management and service-level agreements. The response prioritises internet-facing services, vulnerable NGINX configurations and infrastructure components where exploitation could affect customer workloads or platform availability.

NGINX is also widely deployed inside customer-managed virtual machines, Kubernetes clusters and container images. These environments may operate independently of WAYSCloud's infrastructure maintenance processes and require action from their respective administrators. Infrastructure-level patching does not update NGINX inside those workloads.

This is a proactive security response to publicly disclosed vulnerabilities, not a disclosure of a confirmed compromise of WAYSCloud infrastructure.

Vulnerability Background

NGINX is used across the internet to serve websites, terminate encrypted connections, distribute incoming traffic and route requests to backend applications. It is also frequently deployed as a Kubernetes ingress controller or embedded in application containers.

The most significant vulnerability in the November disclosure is CVE-2026-123007, a memory corruption flaw involving HTTP/2 flow control. An attacker who can establish an HTTP/2 connection to a vulnerable NGINX instance may be able to trigger memory corruption. Depending on the environment and exploit conditions, this can result in worker process crashes or potentially remote code execution without authentication.

The five principal vulnerabilities are:

  • CVE-2026-123007 — HTTP/2 flow control memory corruption
  • CVE-2026-123633 — HTTP/2 connection handling and use-after-free
  • CVE-2026-121810 — HTTP/3 (QUIC) connection handling
  • CVE-2026-123634 — DNS resolver handling in specific proxy configurations
  • CVE-2026-113425 — NGINX mail proxy authentication handling

The same NGINX security release addresses five additional vulnerabilities.

Exploitation conditions differ between vulnerabilities. Not every NGINX installation is necessarily exploitable, and the presence of an affected software version does not automatically establish that every vulnerable feature is enabled.

Nevertheless, the potential consequences are substantial. Successful code execution in a reverse proxy may expose application traffic, sensitive information available to the worker process, or access to connected backend services. Additional vulnerabilities or excessive process privileges could further increase the impact.

Security researchers have publicly demonstrated exploitation of CVE-2026-123007. At the time of CERT-EU's initial advisory on 18 November, no confirmed exploitation in the wild had been reported. This does not eliminate the possibility of subsequent exploitation. Given NGINX's widespread use and the availability of public exploit research, WAYSCloud considers immediate remediation appropriate.

WAYSCloud Security Response

Following disclosure of the vulnerabilities, WAYSCloud initiated an accelerated patching response covering infrastructure and services within its operational responsibility. The response prioritises internet-facing services, vulnerable NGINX configurations and infrastructure components where exploitation could affect customer workloads or platform availability.

WAYSCloud-operated infrastructure and services

Security patching was initiated for WAYSCloud-operated services and infrastructure nodes running affected NGINX components. The response prioritises services exposed to untrusted networks, shared entry points and dependencies supporting customer-facing functionality. Remediation involves deploying the relevant security fixes and verifying that updated NGINX processes are running correctly, followed by service-level checks where necessary.

Shared Hosting

WAYSCloud initiated security updates across its Shared Hosting infrastructure. For NGINX components operated as part of the shared hosting service, operating system and web server maintenance remain within WAYSCloud's management responsibility. Customers using standard Shared Hosting are therefore not expected to independently patch the underlying shared NGINX infrastructure. Customers operating additional, independently deployed application components should still assess whether those components include vulnerable NGINX versions.

Managed services and SLA-covered customer environments

Customer environments covered by explicit operating system, web server or infrastructure management agreements are included in the coordinated patching response according to their agreed service scope. This includes eligible customer servers and services where WAYSCloud has contractual responsibility for maintaining the affected components. The response takes account of application dependencies, deployment requirements and the potential operational impact of applying security updates.

An SLA does not, by itself, imply that every operating system, container or application component is managed by WAYSCloud. Responsibility depends on the specific services covered by the agreement.

Customer-Managed Infrastructure: Action Required

A distinction must be made between the underlying cloud infrastructure operated by WAYSCloud and the operating systems, applications and workloads administered by customers.

Security updates applied to WAYSCloud's infrastructure do not automatically update NGINX installations inside independently managed virtual machines, Kubernetes workloads or container images. Customers operating these environments should review their exposure without delay.

Virtual Private Servers and Virtual Machines

Customers responsible for their own virtual machines must assess NGINX installations running within the guest operating system. This applies regardless of whether the instance is hosted on WAYSCloud Compute, VPS or another infrastructure service. The required action is to identify affected installations, apply appropriate vendor security updates, restart the affected services and verify successful remediation. Operating system vendors may backport security fixes without changing the upstream NGINX version number, so customers should verify the security status of the installed distribution package rather than relying exclusively on the version displayed by nginx -v.

Kubernetes and Container Deployments

Kubernetes environments require particular attention because NGINX may be running inside ingress controllers, reverse proxy containers, application images or other independently maintained components. Updating Kubernetes nodes, the cluster control plane or the underlying cloud platform does not necessarily update NGINX inside running containers. Customers should review the versions and security status of their ingress controllers, Helm releases and deployed container images. Vulnerable images should be replaced with patched versions, and affected workloads should be redeployed.

An additional concern is the retirement of the community-maintained Kubernetes ingress-nginx project in March 2026. The Kubernetes project has confirmed that this implementation no longer receives security fixes. Customers still operating the retired controller should prioritise migration to a maintained alternative rather than assuming that a new security update will become available.

This retirement does not apply to F5's separately maintained NGINX Ingress Controller, which has its own release and security update process. Customers using managed Kubernetes infrastructure from WAYSCloud remain responsible for independently administered ingress controllers and application workloads unless a separate management agreement explicitly includes those components.

Available Security Updates

On 18 November 2026, the NGINX project released patched versions addressing the disclosed vulnerabilities.

  • NGINX Open Source — Stable: 1.30.7
  • NGINX Open Source — Mainline: 1.31.9
  • NGINX Plus: fixed releases available through F5, depending on the release branch

Customers should use the relevant security updates from their operating system distributor or software vendor. The version of a patched distribution package may differ from the upstream version.

Where NGINX is embedded within third-party software, appliance images or Kubernetes controllers, customers should follow the corresponding vendor's remediation guidance.

A security update must also become effective in the running environment. Depending on the installation method, this may require restarting the NGINX service or redeploying affected containers.

Recommended Customer Actions

WAYSCloud recommends that customers operating independently managed infrastructure take the following steps:

  • Identify affected installations: review virtual machines, web servers, reverse proxies, Kubernetes ingress controllers and container images that include NGINX.
  • Prioritise exposed services: give immediate attention to internet-facing instances, particularly those terminating HTTP/2 or HTTP/3 traffic.
  • Apply security updates: install fixed NGINX releases, vendor-patched operating system packages or updated container images as appropriate.
  • Restart and verify: ensure updated executables are running, redeploy affected containers and validate the operational status of dependent applications.
  • Apply temporary mitigations where necessary: disabling HTTP/2 can mitigate CVE-2026-123007 and CVE-2026-123633 while patching is arranged. Disabling HTTP/3 can mitigate CVE-2026-121810. These measures do not address all disclosed vulnerabilities and may affect applications that depend on these protocols, including gRPC services.
  • Review security indicators: examine relevant NGINX error logs, unexpected worker crashes and suspicious process activity. Such indicators do not independently prove compromise, but they may warrant further investigation.
  • Confirm remediation ownership: customers with managed services or SLAs should verify whether their agreement covers the affected NGINX installation, especially where guest operating systems or container workloads are managed separately.

Customers who suspect exploitation should preserve relevant diagnostic evidence and contact WAYSCloud support through their established security or support channels.

Ongoing Remediation and Verification

The WAYSCloud response includes continued review of the applicable infrastructure inventory, deployment of relevant security updates and verification of affected services.

Given the different delivery models across the platform, remediation status must be assessed separately for infrastructure operated directly by WAYSCloud, customer environments covered by management agreements and independently administered workloads.

The initial deployment of a security update does not, by itself, establish that all relevant systems have completed remediation. Verification must account for running software versions, remaining vulnerable components and the operational state of affected services.

Likewise, remediation of WAYSCloud-managed components should not be interpreted as confirmation that all customer-managed virtual machines or Kubernetes workloads have been patched.

Further updates to this report will document verified remediation milestones, material findings and any confirmed customer impact as the assessment progresses.

Security Governance and Shared Responsibility

This disclosure highlights an important aspect of modern cloud security: vulnerabilities in widely deployed infrastructure software frequently cross boundaries between cloud providers, platform operators and customer-managed applications.

A cloud provider may secure its underlying infrastructure while individual customer workloads continue to operate vulnerable software. This is particularly relevant to Kubernetes, where an ingress controller can serve as a critical network entry point while remaining independently deployed and maintained by the cluster administrator.

WAYSCloud's security response therefore combines direct remediation within its managed scope with transparent guidance for customers whose environments require independent action. The objective is not merely to deploy updates within the provider's infrastructure, but to make the scope of responsibility clear and support timely remediation across the broader customer ecosystem.

Closing Statement

The NGINX vulnerabilities disclosed on 18 November 2026 represent a serious security concern due to their potential impact, widespread deployment and the possibility of unauthenticated remote code execution.

WAYSCloud responded by initiating immediate patching of its own services, relevant infrastructure nodes, Shared Hosting and customer environments covered by applicable management and service-level agreements. The remediation and verification activities continue, and this report will be updated as material information becomes available.

Customers operating independently managed virtual machines, Kubernetes clusters or containerised NGINX deployments should not assume that these workloads are protected by infrastructure-level patching. They should review their environments and apply the relevant security updates as soon as possible.

Our commitment remains to respond promptly, communicate transparently and maintain a clear distinction between confirmed operational outcomes, ongoing investigations and customer responsibilities.

External Security References

Affected Services

hostingvpscompute

Timeline

Nov 19, 2026, 09:35 UTC
Action Taken
Public report published. Security patching of WAYSCloud-operated services and infrastructure nodes, Shared Hosting and SLA-covered customer environments is in progress; verification continues. Customer-managed NGINX installations require independent action.