CVE-2026-113425: update NGINX Open Source mail proxy deployments
F5’s CNA record for CVE-2026-113425 gives a public disclosure date of November 18, 2026. F5 rates it Critical at CVSS 4.0 9.2 and High at CVSS 3.1 8.1. The NGINX advisory uses the separate label major.
Choose the corrected branch
For NGINX Open Source, upstream lists 0.5.33 through 1.31.8 as affected, with fixed-branch exceptions: stable 1.30.7 or later and mainline 1.31.9 or later. A stable 1.30.7 installation is therefore outside the affected range despite its lower version number.
This version guidance applies to Open Source. Use the separate product advisory for NGINX Plus or an appliance that bundles NGINX. For distribution packages, obtain the vendor’s explicit CVE status and package build; a backported correction may retain an older upstream version label.
Inventory and update the service
Include dedicated mail gateways in the package inventory; a web-server upgrade does not establish the version running on a separate mail proxy. Record each gateway’s package origin and the service instance that will be restarted.
Preserve a recoverable configuration backup, check package compatibility, and follow the platform’s supported upgrade procedure. Replace or restart the service processes using the corrected executable. Confirm the running instance’s version as well as the installed package; copying a binary onto disk does not replace an existing process.
Verify normal operation
After the update, use an approved account to complete the normal mail-client connection through each gateway. Check the expected upstream service and ordinary authentication result. Review service startup errors before returning the gateway to its usual traffic.
These operational checks complement the package evidence; successful traffic alone does not establish that the CVE is corrected.
Acknowledgements
This post was created with assistance from AI.