Skip to content
CVE-2026-121810: update NGINX Open Source HTTP/3 deployments

CVE-2026-121810: update NGINX Open Source HTTP/3 deployments

November 21, 2026

F5’s CNA record for CVE-2026-121810 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 1.25.0 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.

The lower bound above follows the NGINX advisory. The CNA record instead writes 1.25.09; use upstream’s explicit 1.25.0 bound when assessing older installations. Both sources identify the same corrected branches.

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

Inventory each serving instance and the image or package that supplies it. Keep the existing HTTP/3 service settings in the maintenance record so that a successful update can be checked without changing protocol behavior.

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, make an ordinary request with an approved HTTP/3-capable client and confirm the negotiated protocol. A successful HTTP/1.1 fallback alone does not verify the HTTP/3 service. Check each serving instance before completing the rollout.

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.

Last updated on