CVE-2026-113425: NGINX ngx_mail_proxy_module vulnerability

Published Nov 18, 2026
·
Updated

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

56 affected componentsFixes available
Nginx NGINX Open Source
Nginx NGINX Plus
F5 NGINX Plus>=37.1.0<=37.2.0, >=37.0.0<=37.0.7
37.3.037.0.8
F5 NGINX Plus=34
F5 NGINX Open Source>=1.31.0<=1.31.8, >=0.5.33<=1.30.6
1.31.91.30.7
F5 NGINX Instance Manager>=2.19.0<=2.24.1
2.25.0
F5 F5 WAF for NGINX>=5.9.0<=5.16.1
5.16.25.14.4
F5 NGINX App Protect WAF>=5.4.0<=5.8.0
F5 NGINX App Protect WAF>=4.12.0<=4.16.0
F5 F5 DoS for NGINX>=4.8.0<=4.12.0
4.13.0
F5 NGINX App Protect DoS>=4.5.0<=4.7.0
F5 NGINX Gateway Fabric>=2.0.0<=2.8.1
2.9.0
F5 NGINX Gateway Fabric>=1.5.0<=1.6.2
F5 NGINX Ingress Controller>=1<=2026, =2026
2026--11
F5 NGINX Ingress Controller>=5.0.0<=5.7.1
5.8.0
F5 NGINX Ingress Controller>=4.0.0<=4.0.1
F5 NGINX Ingress Controller>=3.7.1<=3.7.2
F5 Dos Nginx>=4.5.0<=4.7.0
F5 Dos Nginx>=4.8.0<4.13.0
F5 NGINX Gateway Fabric>=1.5.0<=1.6.2
F5 NGINX Gateway Fabric>=2.0.0<2.9.0
F5 NGINX Ingress Controller>=5.0.0<5.8.0
F5 NGINX Ingress Controller>=2026-lts-r1<2026-lts-r11
F5 NGINX Ingress Controller=3.7.1
F5 NGINX Ingress Controller=3.7.2
F5 NGINX Ingress Controller=4.0.0
F5 NGINX Ingress Controller=4.0.1
F5 NGINX Instance Manager>=2.18.0<2.24.0
F5 NGINX Open Source>=0.5.33<1.30.7
F5 NGINX Open Source>=1.31.0<1.31.9
F5 NGINX Plus>=37.0.0<37.0.8
F5 NGINX Plus>=37.1.0<37.3.0
F5 NGINX Plus=r34
F5 NGINX Plus=r35
F5 NGINX Plus=r36
F5 Waf Nginx>=4.12.0<=4.16.0
F5 Waf Nginx>=5.4.0<=5.8.0
F5 Waf Nginx>=5.9.0<5.16.2
ubuntu/nginx<1.4.6-1ubuntu3.9+esm10
1.4.6-1ubuntu3.9+esm10
ubuntu/nginx<1.10.3-0ubuntu0.16.04.5+esm11
1.10.3-0ubuntu0.16.04.5+esm11
ubuntu/nginx<1.14.0-0ubuntu1.11+esm6
1.14.0-0ubuntu1.11+esm6
ubuntu/nginx<1.18.0-0ubuntu1.7+esm5
1.18.0-0ubuntu1.7+esm5
ubuntu/nginx<1.18.0-6ubuntu14.23
1.18.0-6ubuntu14.23
ubuntu/nginx<1.24.0-2ubuntu7.20
1.24.0-2ubuntu7.20
ubuntu/nginx<1.30.4-7ubuntu1.2
1.30.4-7ubuntu1.2
ubuntu/nginx<1.28.3-2ubuntu1.13
1.28.3-2ubuntu1.13
All of the following
azurelinux/nginx<1.30.6-2
1.30.6-2
Microsoft Azure Linux=3.0
alpine/nginx<1.26.3-r4
1.26.3-r4
alpine/nginx<1.28.3-r8
1.28.3-r8
alpine/nginx<1.28.3-r8
1.28.3-r8
alpine/nginx<1.30.7-r0
1.30.7-r0
debian/nginx<=1.22.1-9+deb12u9, <=1.26.3-3+deb13u7, <=1.30.6-3
1.22.1-9+deb12u111.26.3-3+deb13u111.30.6-4
debian/nginx<1.22.1-9+deb12u11
1.22.1-9+deb12u11
debian/nginx<1.26.3-3+deb13u11
1.26.3-3+deb13u11
debian/nginx*

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 37.3.0Fixed in 37.0.8
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 1.31.9Fixed in 1.30.7
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.25.0
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 5.16.2Fixed in 5.14.4
  5. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 4.13.0
  6. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.9.0
  7. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2026-Fixed in -Fixed in 11
  8. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 5.8.0
  9. Upgrade

    Upgrade ubuntu/nginx to a version that resolves this vulnerability.

    Fixed in 1.4.6-1ubuntu3.9+esm10
  10. Upgrade

    Upgrade ubuntu/nginx to a version that resolves this vulnerability.

    Fixed in 1.10.3-0ubuntu0.16.04.5+esm11
  11. Upgrade

    Upgrade ubuntu/nginx to a version that resolves this vulnerability.

    Fixed in 1.14.0-0ubuntu1.11+esm6
  12. Upgrade

    Upgrade ubuntu/nginx to a version that resolves this vulnerability.

    Fixed in 1.18.0-0ubuntu1.7+esm5
  13. Upgrade

    Upgrade ubuntu/nginx to a version that resolves this vulnerability.

    Fixed in 1.18.0-6ubuntu14.23
  14. Upgrade

    Upgrade ubuntu/nginx to a version that resolves this vulnerability.

    Fixed in 1.24.0-2ubuntu7.20
  15. Upgrade

    Upgrade ubuntu/nginx to a version that resolves this vulnerability.

    Fixed in 1.30.4-7ubuntu1.2
  16. Upgrade

    Upgrade ubuntu/nginx to a version that resolves this vulnerability.

    Fixed in 1.28.3-2ubuntu1.13
  17. Upgrade

    Upgrade azurelinux/nginx to a version that resolves this vulnerability.

    Fixed in 1.30.6-2
  18. Upgrade

    Upgrade alpine/nginx to a version that resolves this vulnerability.

    Fixed in 1.26.3-r4
  19. Upgrade

    Upgrade alpine/nginx to a version that resolves this vulnerability.

    Fixed in 1.28.3-r8
  20. Upgrade

    Upgrade alpine/nginx to a version that resolves this vulnerability.

    Fixed in 1.30.7-r0
  21. Upgrade

    Upgrade debian/nginx to a version that resolves this vulnerability.

    Fixed in 1.22.1-9+deb12u11Fixed in 1.26.3-3+deb13u11Fixed in 1.30.6-4
  22. Upgrade

    Upgrade debian/nginx to a version that resolves this vulnerability.

    Fixed in 1.22.1-9+deb12u11
  23. Upgrade

    Upgrade debian/nginx to a version that resolves this vulnerability.

    Fixed in 1.26.3-3+deb13u11

Event History

Nov 18, 2026
Advisory Published
via F5·02:38 PM
Data Sourced
via F5·02:38 PM
DescriptionSeverityWeaknessAffected Software
CVE Published
via OSV·03:23 PM
Data Sourced
via OSV·03:23 PM
DescriptionSeverityAffected Software
CVE Published
via MITRE·03:23 PM
Data Sourced
via MITRE·03:23 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:17 PM
DescriptionSeverityWeaknessAffected Software
Nov 19, 2026
Data Sourced
via Red Hat·06:48 AM
DescriptionSeverityAffected Software
News Published
via BleepingComputer·02:57 PM
Nov 20, 2026
Data Sourced
via Microsoft·09:02 AM
DescriptionSeverityWeaknessAffected Software
Data Sourced
via OSV·09:00 PM
Weakness

Parent advisories

This vulnerability appears in the following advisories.

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

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.

2

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.

3

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.

4

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203