Vulnerabilities in NGINX can allow an attacker to execute code without authentication. Researchers reproduced an attack against an HTTP/2-enabled server serving only static files. Wiz Research
The fixed upstream releases are mainline 1.31.9 and stable 1.30.7. Start with internet-facing NGINX deployments. After updating, verify that the running processes have also been replaced. NGINX security advisories
Vulnerability summary
| Item | Details |
| Name | nginx2root |
| Scope | Five NGINX vulnerabilities and a separate Linux kernel vulnerability |
| Primary vulnerability | CVE-2026-123007: memory corruption in HTTP/2 flow control |
| Affected products | Affected releases of NGINX Open Source, NGINX Plus, and products that include NGINX |
| Severity | F5 rating for the primary vulnerability: CVSS 4.0 9.2 (Critical); CVSS 3.1 8.1 (High) |
| Attack conditions | For the primary vulnerability, an unpatched NGINX instance accepting HTTP/2 connections. Authentication is not required. |
| Potential impact | Code execution with NGINX worker privileges, disclosure or modification of accessible information, and service disruption |
| Exploitation status | Researchers demonstrated exploitation. CERT-EU's November 18 advisory reported no exploitation in the wild. |
| NGINX patches | Mainline 1.31.9 and stable 1.30.7 released |
| Debian stable packages | As of November 19, 2026, 14:00 KST, the official tracker marks trixie packages vulnerable to all five CVEs. See the Debian section below. |
| Linux kernel patch | Xint's explanation, dated as of November 19, states that distribution kernel updates were not yet available. |
CVE stands for Common Vulnerabilities and Exposures. CVSS stands for Common Vulnerability Scoring System. F5 advisory, CERT-EU advisory
Initial code execution through the NGINX vulnerabilities runs with the privileges of the worker process. Xint chained a separate Linux SCTP (Stream Control Transmission Protocol) vulnerability to obtain root privileges on the host. Whether that chain works in another environment depends on the kernel and container configuration. Xint analysis
Affected versions
The ranges below refer to official NGINX releases without the security fixes.
| Vulnerability | Affected versions | Features or configuration to check |
| CVE-2026-123007 | 1.9.5–1.30.6; 1.31.0–1.31.8 | HTTP/2 |
| CVE-2026-123633 | 1.19.7–1.30.6; 1.31.0–1.31.8 | HTTP/2 and upstream connections; associated with low available connection slots |
| CVE-2026-121810 | 1.25.0–1.30.6; 1.31.0–1.31.8 | HTTP/3 and upstream connections; associated with connection cleanup |
| CVE-2026-123634 | 0.6.18–1.30.6; 1.31.0–1.31.8 | resolver, dynamic proxy destinations, and subrequests such as mirror or SSI |
| CVE-2026-113425 | 0.5.33–1.30.6; 1.31.0–1.31.8 | Mail proxy configurations using auth_http and related features |
All five vulnerabilities are fixed in mainline 1.31.9 and stable 1.30.7. Distributions may backport fixes while retaining the upstream version number. Compare the full package version with the supplier's security information. NGINX security advisories, Debian package status
Debian stable packages remain vulnerable in the official tracker
As of November 19, 2026, 14:00 KST, Debian 13 (trixie) is the stable release. The official Security Tracker marks the following trixie packages vulnerable to all five NGINX CVEs in nginx2root. Debian releases, Debian nginx Security Tracker
| Release / repository | nginx source package version shown in the tracker | Status for these five CVEs |
| Debian 13 stable / trixie | 1.26.3-3+deb13u7 | vulnerable |
| Debian 13 / trixie-security | 1.26.3-3+deb13u10 | vulnerable |
| Debian unstable / sid | 1.30.6-4 | fixed; separate from a stable security update |
The CVEs checked were CVE-2026-123007, CVE-2026-123633, CVE-2026-121810, CVE-2026-123634, and CVE-2026-113425. A package's vulnerability status does not establish that every deployment is exploitable. Check the enabled modules, configuration, and access paths.
At the time of the check, the official tracker did not link a stable fixed version or a Debian Security Advisory (DSA) for these five CVEs. The vulnerability records and an unstable fix are available; public information does not establish the internal preparation status of a stable update. Primary CVE record
For servers using Debian packages, refresh the package lists and check the installed version, candidate version, and source repository. Do not judge patch status from an upstream version such as 1.26.3 in nginx -v alone. Compare the full package version, including the +deb13u10 suffix.
sudo apt update
dpkg-query -W -f='${binary:Package}\t${Version}\n' 'nginx*'
apt-cache policy nginx nginx-common
Until a stable fix is confirmed, consider the temporary mitigations below, including disabling HTTP/2 on affected configurations. Disabling HTTP/2 does not address all five vulnerabilities.
How to check whether a deployment is affected
The commands below are for Linux. Check each NGINX instance and container separately.
1. Check the installed version and build options
nginx -v # Check the version nginx -V # Check build options and the default configuration path
| Check | What to verify |
| Version | Whether it falls within an affected range above |
| HTTP/2 support | Whether the build options include --with-http_v2_module |
| Distribution fix | Whether the full package version matches the supplier's fixed package |
An HTTP/2-enabled build alone does not establish exploitability. Check the active configuration and access paths as well. NGINX command-line parameters, Researcher's assessment guidance
2. Identify the executable used by the running service
ps -eo pid,ppid,args | grep '[n]ginx'
If NGINX runs as a systemd service, also check:
systemctl show nginx --property=MainPID --property=ExecStart
- Verify that the
nginxfound in your shell is the executable used by the running service. - For containers, record the running image tag and digest, along with the NGINX version inside it.
- Track the owner and fixed package or image deployment status for each service.
3. Check the configuration and external access paths
sudo nginx -T # Test and print the current configuration files
If the service uses a separate configuration file, run the check with the same configuration options used by that service.
| Check | What to inspect |
| HTTP/2 | http2 on; or the http2 parameter in a listen directive |
| HTTP/3 | QUIC / HTTP/3 listeners |
| Proxy and mail configuration | Features listed in the vulnerability table above |
| External access | Both load-balancer access and direct access to the origin server |
nginx -T reads configuration files from disk. Verify that the running service has loaded that configuration. If a front-end component terminates HTTP/2, separately check the protocol forwarded to NGINX and any directly accessible origin paths. NGINX command-line parameters, Exposure assessment
How to patch
1. Obtain the fix for your installation
| Installation | Required update or action |
| Official NGINX mainline | Update to 1.31.9 |
| Official NGINX stable | Update to 1.30.7 |
| OS distribution package | Apply the distribution's security-fixed package |
| Container | Rebuild and redeploy an image containing fixed NGINX |
| NGINX Plus or a bundled product | Apply the fix supplied for that product |
The official download page lists 1.31.9 and 1.30.7. For a distribution package or bundled product, follow the supplier's fixed-version list instead of treating the upstream NGINX version numbers as universal package requirements. NGINX downloads, F5 product-specific fixes
ZIEN Lens will cover follow-up NGINX and kernel security updates, including checks to perform when applying them. Subscribe to ZIEN Lens to receive those updates.
2. Install the fix, test the configuration, and restart
Development and operations teams should check configuration and module compatibility, essential functions, and rollback procedures before installing the fix.
For NGINX managed by systemd, restart only after the configuration test succeeds. Schedule the restart with the impact on active connections in mind.
sudo nginx -t && sudo systemctl restart nginx sudo systemctl is-active nginx
nginx -s reload alone does not load the new executable. For containers, replace instances with the fixed image and check that no old instances remain. NGINX process control, Researcher's patch guidance
3. Verify the running processes
When the systemd nginx service is running normally, you can inspect the executable used by its master process.
# PID of the current service's master process NGINX_PID="$(systemctl show nginx --property=MainPID --value)" # Path and version of the executable used by the running process sudo readlink "/proc/$NGINX_PID/exe" sudo "/proc/$NGINX_PID/exe" -v # Check for remaining NGINX processes ps -eo pid,ppid,args | grep '[n]ginx'
If MainPID is 0, check service startup status first. For distribution packages, also compare the full package version and supplier's fix history; the executable's version output is not sufficient.
| Owner | Completion criteria |
| Development / operations | Fixed package or image deployed |
| Operations | No old master or worker processes, or containers using the old version, remain |
| Development | Key pages, proxying, authentication, and other service functions work normally |
| Security / operations | Applied version, deployment time, verification results, and outstanding deployments recorded |
Temporary mitigations before patching
1. Disable HTTP/2
On NGINX 1.25.1 or later, apply the following directive in affected server blocks:
http2 off;
Regardless of the version, remove any remaining http2 parameter from listen directives.
# Before listen 443 ssl http2; # After listen 443 ssl;
Test and apply the configuration, then verify that existing HTTP/2 connections have ended. Services that depend on HTTP/2, such as gRPC, may be affected. Researcher's mitigation guidance
| Expected result | What to watch for |
| No new external HTTP/2 connections | A failed connection alone does not prove HTTP/2 has been disabled |
| Existing HTTP/2 connections ended | Old workers may continue serving existing connections after a configuration reload |
| Key functions work normally | Check the impact on HTTP/2-dependent services |
This temporarily mitigates CVE-2026-123007 and CVE-2026-123633. It does not fix the other vulnerabilities. CERT-EU mitigation guidance
2. Restrict other affected features and unnecessary access
| Configuration | Action to consider before patching |
| HTTP/3 | Disable HTTP/3 on affected listeners |
| resolver-related configuration | Consider fixed upstreams to reduce dynamic name resolution at request time |
| Mail proxy | Stop unnecessary external exposure or restrict access to approved sources |
| Directly exposed origin | Allow only the access paths required for the service |
Assess service impact before changing features. Keep access-restricted systems on the patch list. Xint temporary mitigations
3. Check the Linux kernel's SCTP status
uname -r # Running kernel version lsmod | grep '^sctp' # Check for a loaded SCTP module
Xint recommends blocking module loading on hosts that do not use SCTP. An empty lsmod result does not mean SCTP built into the kernel has been disabled.
- Check SCTP usage and the kernel configuration.
- Where SCTP is unused, consider blocking module loading.
- Determine whether an already loaded module needs separate handling.
- Apply the distribution's kernel fix when available and verify the kernel version actually running.
Record NGINX and kernel patch status separately. Xint kernel response guidance
Find NGINX across products and deployment images
Patching one production server can still leave the same vulnerable version in other products or deployment images. Identify the products and services that use NGINX, and record:
- The supplier and full package version
- Products and services containing NGINX, plus container image tags and digests
- Active modules, configuration, and external access paths
- Deployment status of the fix and verification results for running processes
ZIEN's Z-BOM is a supply chain security management platform based on a Software Bill of Materials (SBOM). It links registered components to CVE information, helping teams locate products and versions containing NGINX and identify what needs inspection and patching. Z-BOM
Check those products and services against their active modules, configuration, and external exposure to set remediation priorities. After patching, verify that running processes and images have been replaced with fixed versions, then update the component inventory.
Vulnerability disclosure and patch timeline
Discovery, reporting, and validation dates follow Xint's published timeline. All dates are in Coordinated Universal Time (UTC).
| Date (UTC) | Event |
| 2026년 10월 11일 | Xint researchers discovered the vulnerability. |
| 2026년 10월 16일 | Xint reported the vulnerability to F5 through HackerOne. |
| 2026년 10월 20일 | HackerOne completed validation of the report. |
| 2026년 10월 27일 | The report reached F5's NGINX development team. |
| 2026년 11월 9일 | F5's NGINX development team asked Xint to validate the patch. |
| 2026년 11월 10일 | Xint completed patch validation. |
| 2026년 11월 18일 | NGINX mainline 1.31.9 and stable 1.30.7 were released. Both included fixes for the five NGINX vulnerabilities covered by nginx2root. Mainline release notes · Stable release notes |
References
- NGINX security advisories: affected and fixed versions
- F5 CVE-2026-123007 advisory: severity and affected products
- Xint nginx2root analysis: assessment, mitigations, and the kernel vulnerability
- CERT-EU advisory: attack conditions and response guidance
- Debian releases
- Debian nginx Security Tracker
- Debian CVE-2026-123007
- Debian CVE-2026-123633
- Debian CVE-2026-121810
- Debian CVE-2026-123634
- Debian CVE-2026-113425