Skip to main content Skip to local navigation

Multiple Critical NGINX Remote Code Execution Vulnerabilities (NGINX2Root, NGINX2Shell)

 

A picture containing text  Description automatically generated

 


Information Security Advisory

 

Multiple recently disclosed vulnerabilities affect NGINX, a widely used open-source web server software. The vulnerabilities may allow unauthenticated remote attackers to execute arbitrary code, crash NGINX worker processes, or take control of affected servers under certain conditions. The vulnerabilities are being collectively referred to as NGINX2Root and NGINX2Shell.

Severity level:
CVSS Score: 9.2 / Critical

Description:
Security researchers have identified five critical memory corruption vulnerabilities affecting NGINX deployments that use HTTP/2, HTTP/3, reverse proxy functionality, resolver configurations, or mail proxy services. Successful exploitation may allow unauthenticated attackers to achieve remote code execution with the privileges of the NGINX worker process.

The vulnerabilities include:

  • CVE-2026-123007 - Integer underflow vulnerability in HTTP/2 flow control leading to out-of-bounds memory access.
  • CVE-2026-123633 - Use-after-free vulnerability affecting HTTP/2 reverse proxy deployments.
  • CVE-2026-121810 - Use-after-free vulnerability affecting HTTP/3 (QUIC) deployments using upstream proxy connections.
  • CVE-2026-123634 - Use-after-free vulnerability involving specific resolver and proxy configurations.
  • CVE-2026-113425 - Use-after-free vulnerability in NGINX mail proxy services utilizing authentication mechanisms.

A system may be exposed when one or more of the following conditions are present:

  • HTTP/2 is enabled on an affected NGINX server.
  • HTTP/3 (QUIC) is enabled with upstream proxy configurations.
  • Reverse proxy functionality is used through directives such as proxy_pass, fastcgi_pass, or grpc_pass.
  • The NGINX configuration uses combinations of resolver, proxy_pass, mirror, or SSI directives.
  • NGINX mail proxy services are enabled.

Affected Versions:

  • NGINX Open Source versions prior to 1.30.7 (stable).
  • NGINX Open Source versions prior to 1.31.9 (mainline).
  • NGINX Plus releases 33 through 37 prior to 37.0.8.1 and 37.3.0.1
  • Earlier NGINX releases may be vulnerable depending on configuration and enabled features, with some vulnerabilities affecting versions dating back to NGINX 1.9.5 and earlier.

Impact:
Successful exploitation may allow attackers to:

  • Execute arbitrary code remotely without authentication.
  • Cause memory corruption and worker process crashes.
  • Obtain unauthorized access to systems hosting vulnerable NGINX instances.
  • Potentially escalate compromise through additional operating system vulnerabilities.

Resolution:
Upgrade NGINX immediately to one of the following patched versions:

  • NGINX 1.30.7 (stable)
  • NGINX 1.31.9 (mainline)
  • NGINX Plus Release 37.0.8.1 or 37.3.0.1

Please prioritize patching internet-facing systems running nginx.

Mitigation:
If immediate patching is not possible:

  • Disable HTTP/2 where operationally feasible.
  • Disable HTTP/3 (QUIC) if not required.
  • Review configurations using resolver, proxy_pass, mirror, fastcgi_pass, grpc_pass, and mail proxy services.
  • Restrict access to affected services through network controls and Web Application Firewalls (WAFs).
  • Monitor NGINX servers for unexpected crashes, abnormal process behavior, and signs of exploitation.

References:

 


UIT Information Security



Contact

IT Client Services at askIT@yorku.ca or 416 736 5800

 

PRIVACY POLICY | VISIT WWW.YORKU.CA
This email was sent by: York University, 4700 Keele Street, Toronto, Ontario M3J 1P3

This email is viewed best in Microsoft Outlook for web