F5 NGINX
NGINX ngx_mail_proxy_module 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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 37.1.0, < 37.3.0.1
- >= 37.0.0, < 37.0.8.1
- >= R33, < *
Fixed in 37.3.0.1, 37.0.8.1, *
- >= 1.31.0, < 1.31.9
- >= 1.30.0, < 1.30.7
- >= 0.5.33, < *
Fixed in 1.31.9, 1.30.7, *
Mitigation
Upgrade NGINX Plus to 37.3.0.1 or 37.0.8.1 or * or later.
Upgrade NGINX Open Source to 1.31.9 or 1.30.7 or * or later.
Workaround
Restrict listeners to trusted networks.
References
- Vendor advisory my.f5.com/manage/s/article/K000163931
Timeline
Days relative to CVE publicationFirst public PoC 1 h after publication; not in CISA KEV. First PoC: LLCForge/CVE-2026-113425 (created 18 Nov 2026, found by us: 18 Nov 2026).
PoC repositories
Found on GitHub.1 PoCs
PoCs 1
| Repository | Created | Found by us | Stars | Assessment |
|---|---|---|---|---|
| LLCForge/CVE-2026-113425 | 18 Nov 2026 +1 h | 18 Nov 2026 | 0 | PoC
Flags · score 15
Below the suspicion threshold (50); does not change the assessment. |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.