F5 says undisclosed traffic can trigger the flaw when NGINX Open Source or NGINX Plus is configured as a mail proxy.An unauthenticated remote attacker may crash a worker or corrupt its memory, disrupting service. F5 also lists potential code execution if Address Space Layout Randomization (ASLR) is disabled or the attacker bypasses it. The record identifies a data plane issue without control plane exposure.
What it allows
How Does CVE-2026-113425 Affect the Mail Proxy?
F5 identifies a use-after-free in an NGINX worker processing mail proxy traffic. That class of error means a worker can access memory after it has been released. F5 does not disclose the triggering traffic, so the public record does not support a specific request pattern or reliable detection signature.
The immediate stated outcomes are a worker crash or memory corruption and service disruption. F5 describes code execution as a potential further impact only when ASLR is disabled or bypassed. This distinction matters when prioritizing the patch: the CVSS 4.0 score is 9.2, but the stated code execution path remains conditional.
Our defensive reading is to correlate unexpected mail proxy worker crashes with the affected deployment and its mail listener traffic. A crash by itself does not identify this CVE. Use the vulnerability intelligence platform to organize affected assets and their owners while confirming the actual mail proxy configuration.
Who is affected
Which CVE-2026-113425 NGINX Deployments Need Action?
Exposure requires NGINX Open Source or NGINX Plus configured as a mail proxy through ngx_mail_proxy_module. A server using NGINX only for HTTP traffic is outside the configuration F5 describes. Check the effective configuration and the running binary, including instances reachable only through trusted networks.
NGINX gives versions 0.5.33 through 1.31.8 as a broad vulnerable span, but also marks 1.30.7+ and 1.31.9+ as not vulnerable in their respective branches. F5's CVE record separates the affected 1.30.0 to before 1.30.7 and 1.31.0 to before 1.31.9 branches. It also has an older range beginning at 0.5.33 without a comparable fixed maintenance build.
For NGINX Plus, F5 lists R33 and the 37.0 and 37.1 ranges. Its record gives fixed thresholds of 37.0.8.1 for 37.0 and 37.3.0.1 for the range starting at 37.1.0. The R33 row has no comparable fixed build in that record; confirm its supported upgrade path with F5. F5 says versions past End of Technical Support were not evaluated.
Record configuration alongside version in the vulnerability alert triage workflow. The patch management glossary explains how to track remediation and verification across deployed assets.
Timeline
- 2026-11-18
F5 published the CVE record and NGINX listed fixed Open Source releases.
What to do
-
Identify active mail proxies
Inventory NGINX Open Source and Plus instances using ngx_mail_proxy_module. Record the effective mail listener configuration, network reachability, running binary version and service owner.
-
Install a supported fixed release
Upgrade Open Source to 1.30.7 or 1.31.9 or later in the applicable branch. For NGINX Plus, use the applicable fixed 37.x build and ask F5 for the supported R33 upgrade path.
-
Verify the running build
After reload or restart, confirm the active NGINX binary and workers use the intended fixed release. Check the vendor package build when a distribution backports a fix.
-
Limit exposure during a patch delay
F5 advises restricting listeners to trusted networks. Confirm the effective listener access after the configuration change and keep the release upgrade scheduled.
-
Investigate unexpected worker crashes
Review unexplained mail proxy worker restarts or crashes and correlate them with traffic and system logs. Treat this as a general investigation lead, not a CVE-specific indicator.
What Brandefense can do
- Watch your stack for exploited flaws
Name the vendors and products you run, and Brandefense alerts you when a CVE in them is exploited.
- See CVE-2026-113425 in Brandefense Atlas
The Atlas record of CVE-2026-113425: severity, exploitation status and the sources behind it.
- Vulnerability intelligence platform
Brandefense Vulnerability Intelligence follows which vulnerabilities attackers are using, so your team can patch what is under attack first.
Frequently Asked Questions
Does CVE-2026-113425 affect NGINX used only as a web server?
F5 states that the flaw applies when NGINX Open Source or Plus is configured as a mail proxy. Its CVE record does not identify ordinary HTTP serving as the affected path.
Can an unauthenticated attacker execute code through this flaw?
F5 lists potential remote code execution if ASLR is disabled or bypassed. It also says an unauthenticated attacker may crash a worker or corrupt memory and disrupt service.
Which NGINX Open Source releases fix CVE-2026-113425?
NGINX lists 1.30.7+ and 1.31.9+ as fixed. Verify that the running process, not only the installed package, uses the applicable fixed release.
What can a team do while scheduling the upgrade?
F5 recommends restricting mail proxy listeners to trusted networks. That reduces reachability while the team installs and verifies a supported fixed release.
Sources
- CVE-2026-113425 RecordF5 CNA via CVE Program
- NGINX Security AdvisoriesNGINX
- Known Exploited Vulnerabilities CatalogCISA