CVE-2026-113425·Nginx vulnerability
When NGINX Plus or NGINX Open Source is configured as a mail proxy, undisclosed traffic can cause a use-after-free in an nginx worker process. Additionally, attackers can execute code on systems with Address Space Layout Randomization (ASLR) disabled or when the attacker can bypass ASLR. Impact: A remote unauthenticated attacker may crash an nginx worker process or corrupt its memory, disrupting service. Remote code execution is a potential impact. There is no control plane exposure; this is a data plane issue only. 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 a use-after-free vulnerability in the mail proxy module that can lead to worker process crashes or memory corruption. Organizations running Nginx as a mail proxy should prioritize this update, as remote attackers can exploit this flaw without authentication. If you cannot upgrade immediately, consider disabling the mail proxy module or restricting access to mail-related traffic at the network level. 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 update nginxDefensia detects this vulnerability
How to check if you are affected
- Step 1: Check your installed Nginx version by running: nginx -v
- Step 2: Verify if mail proxy is enabled in your Nginx configuration by checking for 'mail {' blocks in /etc/nginx/nginx.conf or /etc/nginx/conf.d/*.conf
- Step 3: Review worker process crash logs using: journalctl -u nginx -n 50 --grep='segfault\|bus error\|core dumped'
- Step 4: After upgrading, confirm the new version is running with: nginx -v && sudo systemctl restart nginx && sudo systemctl status nginx
- 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-113425 /usr/share/doc/nginx*/changelog.Debian.gz` on Debian and Ubuntu, or `rpm -q --changelog nginx | grep -i CVE-2026-113425` 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-113425?
This vulnerability is a use-after-free memory error in Nginx's mail proxy module that occurs when processing undisclosed types of traffic. An unauthenticated remote attacker can trigger this flaw to crash worker processes or potentially execute arbitrary code.
Is CVE-2026-113425 being actively exploited?
No, this vulnerability is not currently listed on the CISA Known Exploited Vulnerabilities (KEV) catalog, and no public exploits are available at this time.
What versions of Nginx are affected by CVE-2026-113425?
All versions of Nginx Open Source and Nginx Plus prior to version 1.30.7 are affected. The vulnerability only impacts installations configured to use the mail proxy functionality.
How do I check if my server is vulnerable to CVE-2026-113425?
Run 'nginx -v' to get your installed version. If it is below 1.30.7 and your configuration includes mail proxy settings (look for 'mail {' in /etc/nginx/nginx.conf), your system is vulnerable.
Does Defensia detect CVE-2026-113425?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Nginx is installed on a monitored server, CVE-2026-113425 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-113425. Free for 1 server.
Get started free