CVE-2026-113425: NGINX ngx_mail_proxy_module vulnerability
NGINX ngxmailproxymodule vulnerability
Other sources
When NGINX Plus or NGINX Open Source is configured as a mail proxy server, a specially crafted mail session can result in use-after-free in a worker process. Additionally, attackers can execute code on systems with Address Space Layout Randomization (ASLR) disabled or when the attacker can bypass ASLR.
— F5
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.
— Red Hat
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 37.3.0Fixed in 37.0.8 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 1.31.9Fixed in 1.30.7 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 2.25.0 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 5.16.2Fixed in 5.14.4 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 4.13.0 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 2.9.0 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 2026-Fixed in -Fixed in 11 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 5.8.0 - Upgrade
Upgrade
ubuntu/nginxto a version that resolves this vulnerability.Fixed in 1.4.6-1ubuntu3.9+esm10 - Upgrade
Upgrade
ubuntu/nginxto a version that resolves this vulnerability.Fixed in 1.10.3-0ubuntu0.16.04.5+esm11 - Upgrade
Upgrade
ubuntu/nginxto a version that resolves this vulnerability.Fixed in 1.14.0-0ubuntu1.11+esm6 - Upgrade
Upgrade
ubuntu/nginxto a version that resolves this vulnerability.Fixed in 1.18.0-0ubuntu1.7+esm5 - Upgrade
Upgrade
ubuntu/nginxto a version that resolves this vulnerability.Fixed in 1.18.0-6ubuntu14.23 - Upgrade
Upgrade
ubuntu/nginxto a version that resolves this vulnerability.Fixed in 1.24.0-2ubuntu7.20 - Upgrade
Upgrade
ubuntu/nginxto a version that resolves this vulnerability.Fixed in 1.30.4-7ubuntu1.2 - Upgrade
Upgrade
ubuntu/nginxto a version that resolves this vulnerability.Fixed in 1.28.3-2ubuntu1.13 - Upgrade
Upgrade
azurelinux/nginxto a version that resolves this vulnerability.Fixed in 1.30.6-2 - Upgrade
Upgrade
alpine/nginxto a version that resolves this vulnerability.Fixed in 1.26.3-r4 - Upgrade
Upgrade
alpine/nginxto a version that resolves this vulnerability.Fixed in 1.28.3-r8 - Upgrade
Upgrade
alpine/nginxto a version that resolves this vulnerability.Fixed in 1.30.7-r0 - Upgrade
Upgrade
debian/nginxto a version that resolves this vulnerability.Fixed in 1.22.1-9+deb12u11Fixed in 1.26.3-3+deb13u11Fixed in 1.30.6-4 - Upgrade
Upgrade
debian/nginxto a version that resolves this vulnerability.Fixed in 1.22.1-9+deb12u11 - Upgrade
Upgrade
debian/nginxto a version that resolves this vulnerability.Fixed in 1.26.3-3+deb13u11
Event History
Frequently Asked Questions
Which deployments are exposed to this issue?
The issue affects NGINX Plus and NGINX Open Source deployments only when they are configured as a mail proxy server. It is a data plane issue; the control plane is not exposed.
What does an attacker need to exploit it?
A remote attacker does not need authentication or user interaction. Exploitation requires sending specially crafted or otherwise undisclosed traffic through the mail-proxy service, and the attack complexity is rated high.
What is the likely impact if exploitation succeeds?
An attacker may crash an nginx worker process or corrupt its memory, causing service disruption. Remote code execution is also a potential outcome, particularly if ASLR is disabled or can be bypassed.
How does ASLR affect the risk?
ASLR does not remove the underlying use-after-free condition, but it affects code-execution potential. Code execution is described as possible on systems with ASLR disabled or where an attacker can bypass ASLR.