CVE-2026-123634: update NGINX Open Source resolver deployments
F5’s CNA record for CVE-2026-123634 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 medium.
Choose the corrected branch
For NGINX Open Source, upstream lists 0.6.18 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 NGINX instances outside the public web tier in the inventory. Record the package origin and service owner for each instance, and preserve the existing name-resolution settings with the configuration backup.
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 replacing the running processes, check the service’s ordinary upstream connectivity and its normal name-resolution logs. Confirm that expected application traffic still reaches the intended upstreams. Record any resolution failures before completing the maintenance window.
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.