CVE-2026-123634·Nginx vulnerability
This issue occurs when NGINX Plus or NGINX Open Source is configured as a proxy, the proxied server name includes variables, and a Server Side Includes (SSI) or mirror directive sends a subrequest to a location that resolves the same server name. Under these conditions, a specially crafted HTTP request may cause a use-after-free condition in a worker process. An attacker may also be able to execute code if Address Space Layout Randomization (ASLR) is disabled or the attacker can bypass ASLR. Impact: An attacker could leverage this vulnerability to crash the NGINX worker process, corrupt its memory, or perform remote code execution (RCE) Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
- Severity
- high
- Software
- Nginx
- Fixed in
- 1.30.7
- Published
Affected versions
From: 1.9.5
Until: 1.30.6
Fixed in: 1.30.7
How to fix this CVE
Upgrade Nginx to version 1.30.7 or later to patch the use-after-free vulnerability in proxy configurations with variable server names and SSI/mirror directives. This vulnerability can lead to worker process crashes or remote code execution when subrequests are made to locations resolving the same server name. Apply the update immediately to all production systems running affected Nginx versions. Hosted Power publishes patched nginx packages that carry the complete nginx2root fixes for Debian 8 Jessie through 13 Trixie, CentOS 7 (archived EPEL) and CentOS 8 AppStream (streams 1.14, 1.16, 1.18 and 1.20), under the MIT licence: https://github.com/HOSTED-POWER/nginx2root-patches. These are not a mitigation and need no follow-up: each package is that release's own nginx source with every nginx2root patch that applies to it, so nothing further is required. For Debian 8 to 11 and CentOS 7 and 8 no official update is coming at all, which makes them the fix rather than a stand-in. On Debian 12 and 13, where an official update may still ship, the package version deliberately sorts below Debian's expected one (for example 1.22.1-9+deb12u10.1~hp1 on Bookworm) so apt takes over cleanly when it arrives, with no pinning. Patches, checksums, tests and reproducible build instructions are public; we checked the repository on 19 November 2026 (v1.3.2). Note that disabling HTTP/2 does not address the resolver and mail proxy issues in this set. Enterprise Linux is covered too, as of 19 November 2026: RHEL 8 and Rocky Linux 8 (the nginx:1.24 module stream); RHEL 9, Rocky Linux 9 and Oracle Linux 9 across the base 1.20 stream and AppStream 1.22, 1.24 and 1.26; AlmaLinux 9's retired 1.22 stream; and RHEL, Rocky Linux and Oracle Linux 10. On the 10 releases the situation differs by vendor and it matters: AlmaLinux 10 has shipped an official fix, while RHEL 10 and Rocky Linux 10 have not — both still ship nginx 1.26.3-16.el10_3.1, which predates the disclosure. Do not assume a current EL 10 system is patched because a sibling distribution is.
sudo dnf check-update nginx && sudo dnf update nginxDefensia detects this vulnerability
What an exploitation attempt looks like
Sample log line indicative of exploitation attempts:
POST|GET /.*\$.*subrequest|mirror.*ssi HTTP/1\.[01].*\r\nHost:.*\$WAF mitigation (if patching is not yet possible)
Add this rule to your WAF to block exploitation attempts while you schedule the patch.
Block HTTP requests containing multiple variable expansions (e.g., $var syntax) in URL paths when SSI processing is enabled. Implement strict validation of Host header values and reject requests with unusual variable substitution patterns in proxy directives.How to check if you are affected
- Check installed Nginx version: nginx -v or nginx -V for detailed build information
- Verify proxy configuration contains variable server names: grep -r 'proxy_pass.*\$' /etc/nginx/conf.d/ /etc/nginx/sites-enabled/
- Identify SSI or mirror directives in Nginx config: grep -rE '(ssi |mirror )' /etc/nginx/conf.d/ /etc/nginx/sites-enabled/
- Confirm the fix by running nginx -v and verifying version is 1.30.7 or higher after upgrade
- Step 5: If your distribution backported the fix, the version number will not show it. Debian, Ubuntu and the RHEL family ship security fixes inside the existing upstream release — Ubuntu's nginx 1.24.0-2ubuntu7.20 carries this fix and still answers "nginx/1.24.0" — so every version check above, and every external scanner, will keep calling a patched host vulnerable. Read the changelog of the package that is actually installed, which names the CVE: `zgrep -i CVE-2026-123634 /usr/share/doc/nginx*/changelog.Debian.gz` on Debian and Ubuntu, or `rpm -q --changelog nginx | grep -i CVE-2026-123634` on RHEL, Rocky, AlmaLinux and Oracle Linux. Use the file on disk rather than `apt changelog`: that command reads repository metadata, so it describes what the repository holds rather than what you are running, and it does not reliably show third-party packages — including backported ones. A match means this build carries the fix. The reverse does not hold: a CVE absent from the changelog may simply never have applied to that build, so absence is not confirmation that you are exposed.
FAQ
What is CVE-2026-123634?
This is a use-after-free memory vulnerability in Nginx that occurs when the reverse proxy is configured with variable server names and processes SSI or mirror directives. Under specific conditions, it can allow memory corruption or remote code execution.
Is CVE-2026-123634 being actively exploited?
No, this vulnerability is not currently listed in CISA's Known Exploited Vulnerabilities (KEV) catalog, and no public exploits are available. However, the high CVSS score of 8.1 warrants immediate patching.
What versions of Nginx are affected by CVE-2026-123634?
All versions prior to 1.30.7 are affected. The specific version range depends on your Nginx deployment, but all unpatched releases before 1.30.7 contain this vulnerability.
How do I check if my server is vulnerable to CVE-2026-123634?
Run 'nginx -v' to check your version. If it is below 1.30.7 and your Nginx configuration uses proxy_pass with variables combined with SSI or mirror directives, your server is vulnerable.
Does Defensia detect CVE-2026-123634?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Nginx is installed on a monitored server, CVE-2026-123634 will appear in your dashboard with remediation steps.
Related Nginx CVEs
References
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-123634. Free for 1 server.
Get started free