CVE-2026-113425 NGINX ngx_mail_proxy_module vulnerability
Remote unauthenticated attackers can crash or corrupt NGINX workers via the mail proxy module, possibly executing code when ASLR is disabled.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Harmful if only installed
- No
- Needs a specific call
- No
- Fix
- Available
What is CVE-2026-113425?
CVE-2026-113425 is a critical use after free vulnerability in F5 NGINX Open Source, published on 18 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
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.
Weakness: CWE-416
Which versions are affected by CVE-2026-113425?
It affects 7 products.
Only installations with a non-default setting turned on are exposed.
Status by vendor (1)
| Who | Release | Status | Packages |
|---|---|---|---|
| Upstream | fixed | f5:dos (4.13.0), f5:nginx_gateway_fabric (2.9.0), f5:nginx_ingress_controller (2026-lts-r11) and 4 more |
Products include F5 Dos, F5 NGINX Gateway Fabric, F5 NGINX Ingress Controller, F5 NGINX Instance Manager, F5 NGINX Open Source, F5 NGINX Plus and 1 more.
CPE match criteria (21)
| CPE 2.3 | Versions |
|---|---|
cpe:2.3:a:f5:dos:*:*:*:*:*:nginx:*:* | from 4.5.0, up to 4.7.0 |
cpe:2.3:a:f5:dos:*:*:*:*:*:nginx:*:* | from 4.8.0, before 4.13.0 |
cpe:2.3:a:f5:nginx_gateway_fabric:*:*:*:*:*:*:*:* | from 1.5.0, up to 1.6.2 |
cpe:2.3:a:f5:nginx_gateway_fabric:*:*:*:*:*:*:*:* | from 2.0.0, before 2.9.0 |
cpe:2.3:a:f5:nginx_ingress_controller:*:*:*:*:continuous_releases:*:*:* | from 5.0.0, before 5.8.0 |
cpe:2.3:a:f5:nginx_ingress_controller:*:*:*:*:long-term_support:*:*:* | from 2026-lts-r1, before 2026-lts-r11 |
cpe:2.3:a:f5:nginx_ingress_controller:3.7.1:*:*:*:continuous_releases:*:*:* | 3.7.1 |
cpe:2.3:a:f5:nginx_ingress_controller:3.7.2:*:*:*:continuous_releases:*:*:* | 3.7.2 |
cpe:2.3:a:f5:nginx_ingress_controller:4.0.0:*:*:*:continuous_releases:*:*:* | 4.0.0 |
cpe:2.3:a:f5:nginx_ingress_controller:4.0.1:*:*:*:continuous_releases:*:*:* | 4.0.1 |
cpe:2.3:a:f5:nginx_instance_manager:*:*:*:*:*:*:*:* | from 2.18.0, before 2.24.0 |
cpe:2.3:a:f5:nginx_open_source:*:*:*:*:*:*:*:* | from 0.5.33, before 1.30.7 |
cpe:2.3:a:f5:nginx_open_source:*:*:*:*:*:*:*:* | from 1.31.0, before 1.31.9 |
cpe:2.3:a:f5:nginx_plus:*:*:*:*:*:*:*:* | from 37.0.0, before 37.0.8 |
cpe:2.3:a:f5:nginx_plus:*:*:*:*:*:*:*:* | from 37.1.0, before 37.3.0 |
cpe:2.3:a:f5:nginx_plus:r34:*:*:*:*:*:*:* | r34 |
cpe:2.3:a:f5:nginx_plus:r35:*:*:*:*:*:*:* | r35 |
cpe:2.3:a:f5:nginx_plus:r36:*:*:*:*:*:*:* | r36 |
cpe:2.3:a:f5:waf:*:*:*:*:*:nginx:*:* | from 4.12.0, up to 4.16.0 |
cpe:2.3:a:f5:waf:*:*:*:*:*:nginx:*:* | from 5.4.0, up to 5.8.0 |
cpe:2.3:a:f5:waf:*:*:*:*:*:nginx:*:* | from 5.9.0, before 5.16.2 |
How do I fix CVE-2026-113425?
Apply the vendor's patch.
Upgrade to the fixed version. These bugs are found with fuzzing and sanitisers and avoided by memory-safe languages. More about Use after free.
Is CVE-2026-113425 being exploited?
There is no known exploitation of CVE-2026-113425 in the wild and no public exploit code.
Public exploit code: 1 proofs of concept on GitHub.
Other vulnerabilities in F5 NGINX Open Source
Sources
Also known as ALPINE-CVE-2026-113425, AZL-114604, BELL-CVE-2026-113425, DEBIAN-CVE-2026-113425, DHI-psqm-wje2-ft2a-lx5i, ECHO-928d-c286-3e1d and 2 more.